Delete Purchase Order Contract Line Item

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

Description emphasizes permanence ('cannot be undone') twice, aligning with destructiveHint annotation. Adds value beyond annotations by clarifying irreversible behavior. No contradictions with 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?

Contains redundant phrases ('This cannot be undone' and 'Permanently removes...' repeated). Endpoint info is useful but could be streamlined. About 4-5 sentences with repetition.

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 delete operation, the description covers essential info: what it does, permanence, required parameters. No output schema exists, so return values aren't expected. Lacks error handling or permission notes, but adequate for a basic tool.

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 covers all three parameters with descriptions (100% coverage). Description lists required parameters but adds no extra meaning beyond the schema. 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?

Clearly states 'Delete Purchase Order Contract Line Item' and explains it permanently deletes Commitments. Distinguishes itself among many delete siblings by specifying the exact resource type and endpoint.

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 on when to use this tool vs alternative deletion methods. Does not mention prerequisites, conditions, or alternatives. Simply says 'Use this to permanently delete the specified Commitments' without context.

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