get_survey_report

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

Adds 'Authenticated via API key', 'Max 10 concurrent requests', and 'Read-only, safe to retry' beyond annotations. However, 'safe to retry' slightly conflicts with idempotentHint=false, but overall provides additional behavioral context.

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 a clear summary, usage guidance, authentication info, parameter details, and return note. Slightly verbose but not overly so; the info is relevant and earned.

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?

With an output schema present, description sufficiently covers return format. Authentication, concurrency limits, and parameter details are provided. The context is complete given the tool's complexity and sibling toolset.

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 coverage is 0%, but description fully explains both parameters: survey_id (the unique id) and account (optional, with reference to list_accounts). This adds significant value beyond the schema.

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 'Get the report for a single survey' and identifies the specific resource (survey report). It distinguishes from sibling tools like list_survey_reports (which lists reports) and get_survey (survey details).

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?

Explicitly says to use for reviewing response rates and engagement for a specific survey. Provides context on parameters (survey_id, account) but does not explicitly state when not to use or compare to alternatives.

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