delete_duplicates

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

No annotations are provided, so the description bears the full burden of disclosure. It implies mutation ('Remove') but does not detail side effects such as whether the operation is undoable, if it preserves original order, or how it handles empty rows or headers. Critical behavioral context is missing.

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 sentence with no unnecessary words. It directly states the core functionality and optional parameter, achieving maximum 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?

Given three parameters, no annotations, no output schema, and a long list of sibling tools, the description is severely lacking. It does not explain what constitutes a duplicate (e.g., entire row or selected columns), whether the first or last occurrence is kept, or any performance implications. This leaves the agent underinformed for safe and correct usage.

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 coverage is 0%, so the description must compensate. It adds minimal value by explaining 'comparison_columns' can limit comparison to specific columns, but does not explain default behavior (e.g., comparing all columns) or the meaning of 'spreadsheet_id' and 'range' beyond what is obvious from the names.

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 ('Remove'), the resource ('duplicate rows from a range'), and the optional capability ('optionally comparing only column indexes'). It distinguishes this tool from siblings like delete_rows or clear_range by focusing specifically on duplicate removal.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools for data manipulation (e.g., sort_range, clear_range, delete_rows), an agent cannot determine when this tool is appropriate or what the alternatives are.

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