delete_sheet_rows

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions deprecation of filepath and performance preference for session_id, but does not state that the operation is destructive, irreversible, or requires an open workbook. Missing key behavioral details 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 concise: a single sentence for purpose, bulleted args, and a note. No wasted words, well-organized, and front-loaded. Every sentence adds value.

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?

Despite having an output schema (missing details), the description omits prerequisites (open workbook), side effects (persistence), and distinguishes from siblings. For a deletion tool with 5 parameters and no annotations, this is incomplete for reliable agent use.

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%, so the description provides the only parameter documentation. Each parameter has a brief description (e.g., 'Name of worksheet', 'Row number to start deleting from'). Adds context like 'preferred' and 'deprecated' for session_id and filepath. Adequate but not rich.

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 'Delete one or more rows starting at the specified row.' It uses a specific verb (delete) and resource (rows), making the purpose unambiguous. It naturally distinguishes from sibling tools like delete_sheet_columns by specifying '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?

No explicit guidance on when to use this tool versus alternatives like delete_sheet_columns or delete_range. The note about preferring session_id over filepath is internal tool guidance, not selection guidance among siblings. The agent must infer usage context.

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