Export form responses to Sheets

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

With no annotations, the description carries the full load and does a solid job: it discloses deduplication semantics, row migration by answer matching, placement of newly added questions, and a failure mode (reordered columns fail safely). It omits permission/scope requirements and whether the destination sheet must already exist, which keeps it below a 5.

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?

Two dense sentences with zero filler, front-loaded with the core action and then the non-obvious migration semantics. Every clause carries information an agent would otherwise have to discover at runtime.

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?

For a 4-parameter mutation with no output schema, the description covers the hard parts (dedup, migration, failure mode) but leaves open whether the tab is created when absent and what an export returns (row counts, new vs. migrated). Those gaps are minor given the otherwise rich behavioral detail.

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 100%, so formId, account, sheetName and spreadsheetId are already documented in the schema. The description's mention of the ID column and column ordering adds context about write behavior but nothing about parameter formats or the default tab behavior. Baseline 3 applies.

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 opens with a specific verb+resource pair ("Append form responses to Sheets") and adds a distinctive implementation detail (a __google_forms_response_id column). An agent can distinguish it from google_forms_responses (read) and google_sheets_append, though it never names those siblings explicitly.

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?

There is no explicit when-to-use statement or named alternative. Usage is only implied through behavior: the dedup column and row migration tell an agent that repeated exports are safe, but nothing says when to call google_forms_responses instead or what preconditions exist.

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