get_pronunciation_dictionaries_metadata

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing beyond that - no mention of pagination behavior, default page size, or archive handling, despite these being operationally relevant for a list tool.

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?

It is short, but the brevity comes from under-specification rather than efficiency - there is no front-loaded scope, constraint, or routing information. A three-word restatement of the name does not earn its place.

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 five-parameter list endpoint with no output schema, the description should at least sketch what is returned and how paging works. None of that is present, leaving the agent to infer everything from the parameter names.

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 100%, so all five parameters (sort, cursor, page_size, sort_direction, include_archived) are documented in the schema itself. The description adds no additional meaning beyond the schema, which is the baseline-3 expectation when the schema does the heavy lifting.

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 'Get Pronunciation Dictionaries' merely restates the tool name and adds no specificity about scope, filters, or return content. It fails to distinguish itself from the closely named sibling get_pronunciation_dictionary_metadata (singular), which an agent could easily confuse it with.

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?

There is no indication of when to use this list endpoint versus the singular get_pronunciation_dictionary_metadata or update_pronunciation_dictionaries. No prerequisites, pagination context, or filtering guidance is provided.

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