List Requisition (Subcontractor Invoice) Change Order Items

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it returns a paginated JSON array and uses page/per_page for pagination with metadata. This adds some context beyond annotations but does not discuss authorization 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 reasonably concise with several sentences, including a link to filtering documentation. It is front-loaded with the core purpose. However, it could be slightly more streamlined.

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 lacks an output schema and does not fully explain the structure of the returned items. There is an inconsistency: the title says 'change order items' but the description mentions 'Commitments', which could confuse the agent. It provides pagination and filtering info but misses details on response structure. For a listing tool with no output schema, this is insufficient.

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 description coverage is 100%, so baseline is 3. The description mentions required parameters and pagination but does not add meaning beyond what the schema already provides. No additional parameter details.

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 'Return a list of Requisition (Subcontractor Invoice) Change Order Items' with specific verb and resource. It also provides usage context (paginated overview, find IDs, filter). However, it does not differentiate from sibling list tools like list_requisition_subcontractor_invoice_contract_items, which is a minor gap.

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 says 'Use this to enumerate Commitments when you need a paginated overview, to find IDs, or to filter by query parameters' and mentions required parameters. It includes a link to filtering docs. However, it does not explicitly state when not to use this tool or mention alternative sibling tools, so guidance is adequate but not explicit.

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