get_survey_questions_report

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

Adds value beyond annotations by stating read-only, safe to retry, max 10 concurrent requests, and API key authentication. However, there is a minor contradiction: annotations set idempotentHint=false while description claims 'safe to retry', which implies idempotency.

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?

Well-structured with no fluff: purpose statement, brief explanation, auth/rate limit notes, args, return. Front-loaded and easy to parse.

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?

Covers authentication, rate limits, and return format. With an output schema present, additional detail on return structure is unnecessary. Could mention prerequisite that survey must exist, but overall sufficient.

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?

Despite 0% schema description coverage, the description includes a detailed 'Args' section explaining survey_id and account, including examples and cross-reference to list_accounts.

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?

Clear verb+resource: 'Get the questions report for a single survey.' Distinguishes from sibling survey tools by specifying aggregate per-question reporting.

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?

Provides clear use context ('understand how respondents answered across all questions') and mentions authentication and rate limits, but does not explicitly state when to avoid using this tool compared to alternatives like get_survey_responses.

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