create_pronunciation_dictionary

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of disclosing behavior. It explains that the dictionary is saved by name and reusable, and it specifies the return value. However, it does not disclose what happens if a name already exists (overwrite vs error) or any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a clear one-sentence summary, a usage paragraph, a structured args list, and a returns section. Every sentence adds value, and it is appropriately sized given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides a complete picture: what the tool does, how to use the resulting dictionary, the exact parameter formats, and the return value. It even references related tools (generate_speech/speak, save_speaker) for applying the dictionary, making it fully actionable for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully explain the parameters. It does so thoroughly: name is explained as a handle for reuse, rules are detailed with two formats (alias map and IPA phoneme objects) and examples, and description is noted as optional. This compensates completely for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a pronunciation dictionary, with a specific verb ('Create') and resource. It explains the function and provides a concrete use case, making the purpose unmistakable even without explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use the tool (for consistent pronunciation of names/terms) and how to apply the result (pass to generate_speech/speak or pin to a speaker). However, it does not mention alternatives like add_pronunciation_rules or specify when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.