delete-excel-table-row

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

Annotations already mark destructiveHint=true and readOnlyHint=false, so the description's mention of 'delete' reinforces this without adding new behavioral details beyond the zero-based index clarification.

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 short but contains redundancy: the first sentence is repeated as a tip. This reduces efficiency; a single sentence would suffice.

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 description covers the basic operation and key parameter, but lacks context on prerequisites (e.g., table must exist, index must be valid), expected response, or guidance on when to use this tool over similar sibling tools.

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 100% with basic descriptions for each parameter. The overall description adds value by clarifying that the 'index' parameter uses a zero-based row index, which is not explicit in the schema's 'Path parameter: index' description.

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 verb 'Delete' and the resource 'a single row from a formal Excel table', and specifies the key parameter 'by zero-based row index'. This distinguishes it from sibling tools like delete-excel-range (range deletion) and update-excel-table-row (modification).

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., delete-excel-range or update-excel-table-row). It implies usage for formal Excel tables but lacks scenarios or prerequisites.

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