delete_integration_tables

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

With no annotations, the description must disclose behavioral traits. It states the tool deletes resources, which implies destructive action, but does not explain confirm_write, dry_run, or consequences such as reversibility. The presence of safety parameters is ignored, leaving the agent without awareness of safeguards.

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, consisting of a single clear sentence. It is front-loaded with the verb and resource, avoiding unnecessary words. However, it omits essential details, making it arguably too terse for a tool with multiple safety parameters.

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 is highly incomplete for a tool with three parameters and no annotations. It does not explain safety mechanisms (dry_run, confirm_write), the format of payload, or the effect on dependencies. The presence of an output schema does not compensate for missing behavioral context.

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%, and the description provides no information about the parameters. It does not explain how to specify which integration tables to delete, what payload should contain, or how dry_run and confirm_write affect behavior. This is a critical gap.

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'), the resource ('integration tables'), and scope ('one or more'). It is specific and distinguishes from sibling tools like create_integration_table or alter_integration_table. The purpose is unambiguous.

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 or when not to. It does not mention alternatives, prerequisites, or confirmation requirements. The description merely restates the function without contextualizing it relative to other integration table operations.

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