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

Annotations already mark it as destructive and non-idempotent)Skip the safety profile. The description adds valuable context about the approval workflow: first-use may require manager approval, approval granularity (from-now-on vs just-once), and the instruction to regard the card as consent and not re-ask. This goes beyond the annotations without contradicting them.

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 first sentence is a crisp purpose statement. The longer bracket note is relevant and actionable, though slightly verbose with phrases like 'the card is the yes — do not re-ask in chat.' Overall it's compact and stays on-topic.

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 tool has three fully documented parameters and annotations covering destructiveness. The description adds the approval context and write-tier note, which are important for an agent to invoke it appropriately. It doesn't explain error handling or partial failures, but that is not required given the schema and annotations.

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 all three parameters (spreadsheet_id, requests_json, companyId) are already documented. The description's mention of 'formatting, merging' loosely maps to requests_json but adds no specific semantics beyond the schema. Baseline 3 is appropriate.

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 states a specific verb (Perform batch operations), a resource (Google Spreadsheet), and examples (formatting, merging). The word 'batch' distinguishes it from siblings like append_to_sheet and update_sheet. The purpose is immediately clear.

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 implies usage for multi-change spreadsheet operations via the term 'batch' and mentions 'formatting, merging' as typical cases. The approval note gives guidance on when to call (first clear ask) but does not explicitly contrast with alternative tools or specify when not to use it.

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