Update The Due Date For A Requisition (Subcontractor Invoice)

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that only supplied fields are changed and returns the modified object, which is useful. However, it does not mention side effects, permissions, or rate limits. No contradiction 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?

The description is relatively concise at 4 sentences. The first sentence repeats the title, but the second sentence provides the core usage. The API endpoint info is included but could be trimmed without loss.

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 full schema coverage and no output schema, the description includes the endpoint and return behavior. However, it lacks details like the expected date format for 'due_date' or any constraints, making it adequate but not fully complete.

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?

Input schema provides 100% description coverage for all 4 parameters. The description merely lists the required parameters without adding meaning beyond the schema, so the baseline 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?

The description clearly states that the tool updates the due date for a requisition (subcontractor invoice). The verb 'update' and the specific resource are obvious. However, it does not explicitly distinguish this tool from the sibling 'update_requisition_subcontractor_invoice', which likely updates multiple fields.

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 tool versus alternatives like 'update_requisition_subcontractor_invoice' or other update tools. The description only says 'Use this to update an existing Commitments' without addressing when not to use it.

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