delete_banding

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

The description describes a destructive action but provides no additional context about effects, authorization requirements, or error handling. Without annotations, the description bears full responsibility but adds no behavioral details.

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?

Single sentence, very concise. However, it may be too terse for a 2-param tool. Still, it is front-loaded.

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 2 required parameters, no output schema, and no annotations. The description is too sparse to fully guide an agent. Missing: return value, error scenarios, prerequisite steps (e.g., must have valid IDs).

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%, and the description only says 'by ID' without clarifying which parameter is the ID. Both parameters (spreadsheet_id, banded_range_id) are required, but the description adds no meaning or format guidance.

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?

Description clearly states the action (Delete) on the resource (banding) using an identifier. It distinguishes from sibling tools like add_banding and update_banding.

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?

No explicit guidance on when to use or when not to use. The context of 'by ID' implies that the agent must have a banded_range_id, but no alternatives or conditions are mentioned.

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