delete_table

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

With no annotations, the description must fully disclose behavior, but it only says 'delete'. It does not mention consequences (e.g., data loss), reversibility, permissions required, or side effects like breaking references. The description is minimal.

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 (one sentence), but it misses opportunities to add useful information without being verbose. It could include parameter details or usage notes while remaining brief.

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 large set of sibling tools, the description is insufficiently complete. It lacks prerequisites, return value, and behavioral context. With no output schema, the AI cannot anticipate the result of deletion.

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 0%, and the description adds no meaning to the parameters. It mentions 'by ID' but doesn't explain what table_id or spreadsheet_id represent. The schema only lists names and types, leaving the AI with no semantic guidance.

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' and the resource 'table', with 'by ID' specifying the identifier. It distinguishes from sibling tools like delete_rows, delete_columns, etc., but could clarify what constitutes a 'table' in this context (e.g., a structured table in Sheets).

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 guidance is provided on when to use this tool versus alternatives like delete_rows, delete_range, or delete_chart. The description lacks context on when deleting a table is appropriate, leaving the AI to guess.

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