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

No annotations are provided, so the description carries the full burden. It only says 'append' without disclosing side effects, permission requirements, or whether data is appended to the end of the tab. For a mutation tool with no annotation coverage, this is a significant gap in behavioral transparency.

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 a single, front-loaded sentence that states the purpose and key usage guidance without any redundant or filler content. Every part earns its place, making it exemplary in conciseness.

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?

The description explains the core operation and parameter usage, but with no output schema and no annotations, it lacks behavioral context such as return values, error conditions, or side effects. It is adequate for a simple append tool but leaves some gaps for an agent to fully understand the tool's behavior.

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?

The schema covers all parameters, but the description adds meaningful value by clarifying the distinction between 'rows' (multiple rows) and 'values' (single row). This goes beyond the schema descriptions and helps the agent choose the correct parameter format.

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 action: 'Append one or more rows of data to a spreadsheet tab.' It specifies the resource type (spreadsheet tab) and distinguishes it from sibling append tools like append_slides and append_to_document by explicitly mentioning spreadsheet/Excel/workbook tabs.

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 clear context for when to use this tool (appending data to a spreadsheet tab) and offers parameter guidance ('Use 'rows' for multiple rows or 'values' for a single row'). It does not explicitly state exclusions or when-not conditions, but the resource clarity effectively differentiates it from alternatives.

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