Delete Cost Items

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

Annotations already indicate destructiveHint=true. The description adds emphasis by repeating 'cannot be undone' and 'permanently delete,' but does not disclose additional behavioral traits such as error handling or side effects beyond what annotations provide.

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 verbose with repeated phrases ('cannot be undone' appears twice), but it includes useful context like the API version and endpoint. Could be more concise by removing duplication and focusing on essential usage details.

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?

Covers basic operation and permanence but fails to define the required body parameter. Without output schema, it omits response details. Overall adequate but incomplete for a tool that expects additional input not captured in the schema.

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 coverage is 100% for company_id, but the description adds no new semantics for that parameter. It introduces an undocumented 'array of item IDs' for the request body, which is not in the schema, potentially leading to incorrect invocations.

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 that the tool permanently deletes Cost Catalog records and specifies the endpoint. However, it mentions a request body of item IDs that is not included in the input schema, which may confuse an agent relying solely on the schema.

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 bulk delete tool versus the singular 'delete_cost_item' sibling. The description only states what the tool does, not why one would choose it over alternatives.

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