delete-excel-table-row

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

Annotations already declare destructiveHint=true, so the description does not need to restate that. It adds meaningful context by specifying the zero-based row index and that it applies to a formal Excel table, which goes beyond the annotations and helps the agent understand the deletion semantics.

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 extremely concise—two sentences with no wasted words. The purpose is stated upfront, and the tip adds a key detail in a scannable format with an emoji. Perfectly sized for quick parsing.

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?

For a delete operation, the description covers the essential action and target. It does not describe return values, but no output schema exists and delete responses are typically minimal. The parameters are well-documented in the schema, and the zero-based index detail fills a critical gap. It is complete enough for an agent to call correctly.

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%, so the baseline is 3. The description adds value by clarifying that the 'index' parameter is zero-based, which is not obvious from the schema's generic 'Value for the index path segment.' This specific detail improves parameter understanding.

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 an Excel table row' with a specific verb and resource. The tip adds that it targets a single row in a formal Excel table by zero-based index, distinguishing it from range operations and sibling tools like update-excel-table-row.

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 such as update-excel-table-row or list-excel-table-rows. The tip clarifies the index semantics but does not explain when deletion is appropriate or when other tools should be chosen instead.

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