Remove Change Order Package From A Requisition (Subcontractor Invoice)

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

The description emphasizes that the action is permanent ('cannot be undone') and involves deletion, which aligns with the destructiveHint=true annotation. However, it adds no new behavioral information beyond what the annotations already provide, such as side effects or permission requirements.

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 relatively short but contains redundancy: 'This cannot be undone' and 'Permanently removes the specified Commitments' each appear twice. While not overly lengthy, this repetition reduces 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?

The description explains the core action and its irreversibility, but it lacks details on prerequisites, parameter relationships, and return value. Given that there is no output schema and the tool is destructive, more context on what happens to associated objects would improve 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 description lists the required parameters but does not add any additional meaning beyond the input schema. The schema already provides descriptions for all four parameters (100% coverage), so the description's repetition offers no new semantic value.

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 action: 'Remove a specified Change Order Package from a Requisition (Subcontractor Invoice).' It specifies the verb (remove), resource (Change Order Package), and context (Subcontractor Invoice). The name and title further reinforce this, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It only states what the tool does and lists required parameters. There is no mention of when not to use it, or references to sibling tools like 'add_change_order_package_to_a_requisition_subcontractor_invoice' or 'update_change_order_package'.

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