Delete Catalog

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description reinforces permanent deletion ('cannot be undone') but does not disclose any additional behavioral traits beyond what annotations provide. The idempotent annotation is present but not mentioned. No contradiction, but the description adds little new behavioral context.

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 contains some repetition ('permanently delete' and 'cannot be undone' appear twice). It is front-loaded with the title but could be more concise. The inclusion of endpoint info is useful, but the redundancy slightly hurts conciseness.

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 tool with annotations, the description sufficiently covers purpose, required parameters, and endpoint. It explains the irrevocable nature. It lacks mention of idempotency (present in annotations) but overall is adequate for an agent to invoke correctly.

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?

Input schema includes two parameters with descriptions and 100% coverage. The description lists required parameters (catalog_id, company_id) but does not add meaning beyond the schema. For high schema coverage, the baseline score of 3 is appropriate.

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 tool's purpose: to permanently delete Cost Catalog records. It includes specific verbs ('delete', 'permanently removes') and identifies the resource ('Cost Catalog records'). The API endpoint further clarifies scope. This differentiates it from other delete tools in the sibling list.

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 explicitly says 'Use this to permanently delete the specified Cost Catalog records,' which is a clear when-to-use statement. However, it provides no guidance on when not to use it, nor does it mention alternatives among the many sibling delete tools. This minimal guidance earns a 3.

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