get_survey_question_answers

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

Annotations declare readOnlyHint=true and destructiveHint=false; the description adds 'Read-only, safe to retry' and rate limit info, amplifying transparency without contradiction.

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 optimally concise: a one-line purpose, a clarifying paragraph, a parameter list, and a return statement. Every element is essential and front-loaded.

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?

Given the tool's moderate complexity (5 params, 2 required, read-only), the description covers purpose, guidelines, auth, rate limits, all parameter semantics, and return type, with no missing information.

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?

With 0% schema description coverage, the description's docstring-style parameter list adds critical meaning (e.g., 'account: Optional account name...') beyond the bare schema titles, effectively compensating.

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 it lists answers for a single survey question ('List answers for a single survey question'), distinguishing it from sibling tools like 'get_survey_response' or 'get_survey_responses' which cover different scopes.

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 provides clear guidance on pagination ('Use count and offset to page through large result sets'), authentication ('Authenticated via API key'), and rate limits ('Max 10 concurrent requests'), but lacks explicit when-to-use vs. sibling tools.

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