list_survey_reports

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds key behavioral details: authentication via API key, max 10 concurrent requests, and that it's safe to retry. No contradictions with annotations.

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 concise at about 8 lines, with the main purpose front-loaded. It includes an 'Args' section. Slight redundancy between the first two sentences, but overall efficient.

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 has 3 parameters with 0% schema coverage and an output schema exists, the description adequately covers pagination, authentication, rate limits, multi-account support, and idempotency. It provides all necessary context for correct usage.

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 fully explains all three parameters: count and offset for pagination with defaults, and account for multi-account setup. It adds meaning by providing context on usage and the account naming convention.

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 'List reports for all surveys' and 'Retrieves aggregate performance reports across every survey in the account,' specifying the verb (list) and resource (survey reports). It distinguishes from siblings like get_survey_report, which retrieves a single report.

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 pagination guidance ('Use count and offset to page through large result sets') and account selection instructions. It includes authentication and concurrency limits. However, it does not explicitly state when to use this tool over alternatives like get_survey_report.

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