delete_table

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

Discloses the error condition (IndexError) and the indexing scheme, but does not mention any other side effects or preconditions (e.g., document must be open). Annotations are absent, so the description carries full burden.

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?

A single sentence that is front-loaded with the verb and resource, conveying all essential information without waste.

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 simple nature of the tool (one parameter, deletion operation) and the presence of an output schema, the description adequately covers usage and error handling. Could mention that the table and its content are removed.

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 compensates by clarifying that table_idx is a 0-based index. No further details needed for a single integer parameter.

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 action ('Delete a table') and specifies the resource ('by index (0-based)'). It distinguishes from sibling tools like delete_table_row or delete_column_from_table by targeting the entire table.

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 explicit guidance on index being 0-based and the error behavior (IndexError). Could be improved by explicitly contrasting with related table deletion tools.

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