list_form_responses

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination ('pagination info') and that it returns 'basic details', but lacks critical information: whether this is a read-only operation, what permissions are required, how errors are handled, rate limits, or the exact format of the returned string. For a tool with 5 parameters and no annotation coverage, this is insufficient.

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 appropriately sized and well-structured with clear sections (Args, Returns). The first sentence states the purpose directly, and subsequent sentences add necessary parameter and return details without redundancy. However, the omission of the 'service' parameter in the Args section slightly reduces efficiency.

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 (5 parameters, no annotations, no output schema), the description is incomplete. It lacks behavioral context (e.g., safety, permissions), doesn't document all parameters ('service' is missing), and provides minimal detail on return values ('str' with 'basic details' is vague). For a tool that likely interacts with user data and supports pagination, more guidance is needed.

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 description coverage is 0%, so the description must compensate. It documents 4 parameters (user_google_email, form_id, page_size, page_token) but omits the 'service' parameter entirely. While it adds basic semantics like 'Required' for user_google_email and defaults for page_size/page_token, it doesn't explain what 'service' is or provide format details (e.g., what constitutes a valid form_id). The description partially compensates but leaves one parameter undocumented.

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 the verb ('List') and resource ('a form's responses'), making the purpose specific and understandable. However, it doesn't differentiate this tool from potential siblings like 'get_form_response' (which appears to retrieve a single response) or 'get_form' (which retrieves form metadata).

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 no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_form_response' for single responses or 'get_form' for form metadata, nor does it specify prerequisites or appropriate contexts for listing responses.

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