Delete Direct Cost Item

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

Beyond annotations (destructiveHint: true), the description adds that concurrent requests are not supported and a 409 Conflict error will occur if conflicts arise. This provides useful context beyond what annotations alone convey.

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 front-loaded but contains repetition ('This cannot be undone' appears twice, 'Permanently removes' appears twice). It is not excessively long but could be more 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?

While it explains the core behavior, permanent deletion, and conflict handling, it lacks information about the return value (no output schema) and authorization requirements. Given the absence of an output schema, more detail on the response would enhance completeness.

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 covers both parameters with descriptions and required status (100% coverage). The description merely restates them as required without adding new semantic details, meeting the baseline.

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 it deletes a specific Direct Cost Item and its Line Items, using a specific verb (delete) and resource. It distinguishes itself from siblings like 'delete_direct_cost_line_item' by including the relationship with line items.

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?

While the description mentions 'Use this to permanently delete', it does not provide explicit guidance on when to use this tool versus alternatives like 'delete_direct_cost_line_item' or other delete tools. The usage context is implied but not compared.

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