delete_catalog_ad_item

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Delete' and gives no indication whether the operation is permanent, reversible, or cascades to related entities. This is a significant gap for a destructive operation.

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 a single concise sentence with zero wasted words, making it efficient. However, it lacks any structural elements like context or examples, which limits its usefulness beyond being a tautological phrase.

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 tool is simple with one parameter and no output schema, but the description omits essential operational context such as whether deletion is permanent, how it differs from draft deletion, and what happens to associated data. This is incomplete for a destructive tool in a complex domain.

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 input schema already provides a description for the only parameter 'id' ('Ad item ID'), and coverage is 100%. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate per the rubric.

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 object (catalog ad item), which is a specific verb+resource combination. However, it does not distinguish between deleting a live vs. draft catalog ad item, especially given the sibling tool draft_delete_catalog_ad_item.

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 usage guidance is provided. The description does not explain when to use this tool versus the draft deletion variant, nor does it mention any prerequisites or consequences that would inform the user's decision.

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