remove_duplicates

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

Discloses that only values are compared (not formatting), rows shift up, freed rows are cleared, and header can be preserved. No annotations provided, so description carries full burden – adequately transparent.

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?

Concise, front-loaded with main action, every sentence adds value. No redundancy.

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?

Covers key behaviors, parameters, and edge cases (e.g., case sensitivity, header). No output schema, but return value is implied. Slightly lacking in session_id context but overall complete.

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?

Explains columns and has_header well, but session_id and range are not described (schema coverage 0%). Baseline 3 due to partial compensation, but missing parameter context lowers score from 4.

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 tool deletes duplicate rows within a range, keeping first occurrence. It specifies optional columns and header handling, distinguishing it from sibling tools like clear_range or delete_rows.

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?

Provides clear guidance on column specification and header behavior, and notes case-insensitive comparison. Does not explicitly compare to alternatives but context is sufficient.

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