get_survey

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

Annotations already declare readOnlyHint=true, so read-only is known. Description adds extra behavioral details: authentication via API key, max 10 concurrent requests, safe to retry, and 404 error on invalid IDs. This provides useful context beyond annotations, though annotations already cover the core trait.

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 clear sections (purpose, usage, auth/limits, error info, args, returns). Every sentence adds value, but could be slightly more concise without losing meaning.

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 complexity and sibling tools, the description covers all needed aspects: purpose, parameters, output, error handling, auth, rate limits, and alternatives. No gaps remain.

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 has 0% coverage (no descriptions), but description fully explains each parameter: list_id from list_audiences, survey_id from list_surveys, account with optional account name and reference to list_accounts. Also describes return structure of the JSON survey object.

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?

Description clearly states 'Retrieve full details for a single survey' and specifies it returns questions, status, URL. It differentiates from sibling tools like list_surveys (which lists) and publish_survey/unpublish_survey (which change status).

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 'Use when you have a survey_id (from list_surveys) and need its questions, status, or public URL.' Also directs to use publish_survey/unpublish_survey for changing live status, providing clear when-to-use and alternatives.

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