Delete A Direct Cost Line Item

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description adds the concurrency restriction and 409 error behavior. It reinforces the permanent, irreversible nature of the deletion without contradicting annotations.

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 redundant phrases like 'This cannot be undone' and 'Permanently removes' repeated. The API endpoint info could be omitted. It would benefit from tighter editing.

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?

Given no output schema, the description covers concurrency and error handling but omits return values or success indicators. It adequately describes the operation but leaves some context gap.

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 100% of parameters with descriptions, so the description adds little extra meaning. It mentions required parameters by name but does not enhance understanding beyond the schema.

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 line item, distinguishes from siblings like delete_direct_cost_item, and specifies required parameters. The verb 'delete' combined with the resource 'Direct Cost Line Item' is precise.

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 advises against concurrent requests and explains the 409 Conflict scenario, providing a clear context for when to use. It lacks explicit comparison to alternatives like deleting the entire direct cost item.

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