delete_rows

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

The description mentions that rows below shift up, which is a key behavioral trait. However, with no annotations, it omits other important details like whether the operation is reversible, permissions required, or side effects. More context is needed for a deletion tool.

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 very concise and front-loaded with the action. However, it misses the opportunity to add parameter information in a compact way. Still, it avoids verbosity.

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 the tool's destructive nature, lack of annotations, and missing output schema, the description is incomplete. It does not address edge cases (e.g., invalid row number, zero count) or provide usage context. Sibling tools provide some context but the description itself is insufficient.

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 has 4 parameters (row, count, sheet, session_id) with 0% description coverage. The description does not mention any parameters, leaving agents to infer semantics from names and types alone. For example, 'count' defaults to 1 but its purpose is not explained.

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 rows starting at a given 1-based row number, and that rows below shift up. This distinguishes it from siblings like 'delete_columns' and 'clear_range' which have different purposes.

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 deleting rows, but no explicit guidance on when to use this tool vs alternatives like 'clear_range' or 'delete_sheet'. The sibling list includes related tools, but the description does not differentiate them.

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