delete_catalog

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

With no annotations provided, the description fully bears the burden of disclosing behavior. It explicitly states that the operation is permanent, deletes 'all its data,' and cannot be undone, which are critical behavioral traits. It also mentions the return value, covering the basic behavioral expectations.

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 compact and front-loaded with the most important warning, followed by args and returns in a clean list. Every sentence contributes essential information, with no filler or repetition.

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 simple two-parameter delete operation with an output schema present, the description covers the key elements: purpose, destructive scope, irreversibility, parameter definitions, and return type. It is sufficiently complete for an agent to safely invoke the operation.

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?

The schema has zero description coverage, so the description compensates by explaining 'hostname' as 'Server hostname' and 'catalog_id' as 'ID of the catalog to delete.' While the hostname explanation is somewhat generic, it adds value beyond the bare schema titles and clarifies each parameter's role.

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 opens with 'PERMANENTLY DELETE a catalog and all its data,' which uses a specific verb and resource, and the warning 'Cannot be undone' distinguishes it from other catalog operations. This clearly separates it from sibling tools like delete_catalog_alias or cancel_task.

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?

The description provides clear context by stating the irreversible, destructive nature of the operation, implying it should only be used when permanent deletion is intended. However, it does not explicitly mention alternative tools for deleting catalog aliases or other scoped deletions, so it lacks explicit exclusions.

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