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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the return shape, 1-based paging, and default/max page size, which an agent needs to page correctly.

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?

Front-loaded with the purpose, then return shape, id semantics, and pagination rules in sequence with no filler. It is dense and slightly packed, but every clause adds actionable information.

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 three-parameter search tool it covers purpose, id semantics, downstream consumers, and pagination. The return-shape sentence is technically redundant against the output schema but harmless, and nothing an agent needs to call or page it 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?

Schema description coverage is 0%, so the description must carry the load. It does: query is characterized as matching by name, style or accent, page is stated as 1-based, and pageSize is given a default of 30 and a max of 100. Only the exact query syntax (substring vs fuzzy) is left unspecified.

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?

States a specific verb (Searches) and resource (curated list of AI-tester voices) plus the search dimensions (name, style, accent). It also ties itself to the sibling tools that consume its output, so an agent can place it precisely in the workflow.

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?

Clearly explains the downstream purpose: the returned voiceId feeds audienceSpec.voice.voiceIds in propose_usability_test and edits.audience.voice.voiceIds in revise_usability_test, and warns that voice names are not valid ids. It does not state explicit exclusions or when NOT to call it, so it stops short of a 5.

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