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

Annotations already mark readOnlyHint=false, destructiveHint=true, and idempotentHint=false. The description adds meaningful behavioral context about the write-tier approval flow (manager approval, recurring vs one-time approval) and the instruction not to re-ask, which is beyond the annotations.

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 core description is one sentence, immediately stating the action. The additional approval block is somewhat long but provides essential usage context, so no sentence is wasted.

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 simple append operation, the description covers the action, the spreadsheet target, and the approval side-effect. It doesn't need to explain return values since there is no output schema, and the parameters are fully documented in schema. It is complete enough for correct invocation.

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 input schema already provides descriptions for all three parameters at 100% coverage. The description adds no further parameter meaning, so 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 ('Append') and resource ('Google Spreadsheet'), clearly identifying the operation. It doesn't explicitly distinguish from siblings like batch_update_spreadsheet or update_sheet, but 'append' is a distinct operation; still, no sibling differentiation is provided.

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 explicit guidance on the approval workflow: 'first use may require a manager's approval...' and instructs to call it on the first clear ask. However, it gives no guidance on when to prefer this tool over siblings like update_sheet or batch_update_spreadsheet, leaving tool selection ambiguous.

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