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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description does not need to repeat those facts. It adds value by disclosing the exact return shape: a list of dicts with keys for arpabet, ipa, example, and category. No contradiction with annotations exists.

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 front-loaded with the core verb and resource, followed by structured return details. The Returns block partially overlaps the introductory 'including' list, but this redundancy is acceptable because there is no output schema to document the payload.

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?

For a zero-parameter, read-only inventory endpoint with no output schema, the description is functionally complete: it defines the result type, all fields, their types, and the category values. The annotations cover safety and idempotence, so nothing needed to call the tool correctly is missing.

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?

The tool has zero parameters and the input schema confirms an empty properties object, so there is no parameter behavior to explain. The description correctly avoids inventing parameter details and passes the baseline for parameterless tools.

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 uses a specific verb ('Get') and clearly identifies the resource ('full phoneme inventory supported by the pronunciation scorer'). It also lists the returned fields, which distinguishes it from service-status or speech-processing sibling tools.

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 intended use case is clear: call this when you need the set of phonemes the scorer can assess. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous and distinct from the sibling tools.

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