Six quantum circuit generation tools with minimal parameter validation and weak descriptions. Four tools have zero parameters (bell_state, deutsch_constant, deutsch_balanced, three_qubit_bitflip_code), making them trivial. Two tools accept parameters (bernstein_vazirani: string 's', quantum_teleportation: integer 'n') but parameter descriptions are buried in docstrings, not in schema. Descriptions are adequate (50-100 chars) but generic, they state WHAT the tool returns (OpenQASM string) but not WHEN to use it or what the quantum algorithm does. No output schema documented. No error handling guidance. Tool names are descriptive (verb_noun pattern) but lack action verbs, 'bell_state' is a noun phrase, not 'generate_bell_state'.

• Add parameter descriptions to bernstein_vazirani and quantum_teleportation schemas. Example: 's': {'type': 'string', 'description': 'Binary secret string (0s and 1s only, 1-16 chars). Encodes the oracle function.'}
• Rename tools to start with action verbs: 'generate_bell_state', 'generate_deutsch_constant_oracle', 'generate_deutsch_balanced_oracle', 'generate_bernstein_vazirani_circuit', 'generate_three_qubit_bitflip_code', 'generate_quantum_teleportation_circuit'.
• Expand descriptions to 100-200 chars explaining WHEN to use each algorithm. Example for bell_state: 'Generate a Bell state circuit demonstrating quantum entanglement. Use this to teach entanglement or test two-qubit gates.'
• Document output schema: all tools return a string (OpenQASM 2.0 code). Add explicit return type annotation and note that the string is valid Qiskit qasm2.loads() input.
• Add parameter constraints: bernstein_vazirani 's' must match regex ^[01]+$ and be 1-16 chars; quantum_teleportation 'n' must be 1-10 (integer). Include these in descriptions and validate in code.