get_form_response

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

With no annotations, description carries full burden. It discloses the OAuth scope requirement, implying read-only access (scope is readonly). While it doesn't explicitly state 'read-only' or 'no side effects', the scope and fetch operation imply non-destructiveness. Could be more explicit but still adds useful 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?

Description is three short paragraphs. First sentence states purpose, second provides usage guidance and alternatives, third lists OAuth scope. No filler, every sentence earns its place. Front-loaded with purpose.

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?

Output schema exists, so return value documentation is handled. Description covers usage context, alternatives, and auth requirements. It does not address error handling (e.g., invalid responseId) but for a simple fetch tool this is acceptable. Slightly incomplete but sufficient for the complexity level.

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 100%, all parameters have descriptions. Description adds meaning by explaining response_id as 'opaque string not the same as row number' and links to list_form_responses for source. It also explains the output structure ('keyed by question ID') and how to map questionId via get_form, adding 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?

Description clearly states 'Fetch a single submitted response to a Google Form, including all answers keyed by question ID', which specifies verb and resource. It distinguishes from sibling tools by explicitly mentioning when to use 'list_form_responses' for bulk listing and 'get_form' for question ID mapping.

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?

Description explicitly says 'Use this when you already know the specific responseId' and provides alternatives: 'For bulk listing... use list_form_responses' and 'To look up which questionId maps to which question prompt, call get_form'. Clear guidance on when and when not to use.

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