delete_table

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

No annotations provided, and the description only says 'Delete' without detailing behavioral effects like permanent deletion, implications of 'hard_delete' or 'recursive', or any side effects. The agent cannot infer the tool's full impact from this description.

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 short (one sentence) but it is under-specified for the tool's complexity. It sacrifices useful detail for brevity, making it insufficient rather than concise.

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 absence of annotations, output schema, and param descriptions, the description should compensate. However, it only provides the basic operation and leaves many important aspects (return value, side effects, parameter behavior) unexplained, making it incomplete for effective use.

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?

With 0% schema description coverage, the description fails to explain any of the three parameters. While parameter names are somewhat self-explanatory, 'hard_delete' and 'recursive' could benefit from explicit clarification, which is absent.

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 ('a table') within a specific system ('OpenMetadata'). It is specific and unambiguous, though it does not differentiate from other delete tools but since the resource is different, it is sufficient.

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 on when to use this tool over alternatives, prerequisites, or conditions. The description lacks context about soft vs. hard deletion, or the effect of the 'recursive' parameter.

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