List Prime Change Order Line Items

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

Annotations (readOnlyHint: true, destructiveHint: false) already indicate safe read behavior. The description adds information about pagination, metadata, and the required parameters, which is moderately useful but does not disclose any additional behavioral traits beyond 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 two sentences, but the second sentence is somewhat redundant and contains a minor inaccuracy ('Prime Contracts' instead of 'line items'). It is front-loaded with the core purpose.

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 does not include an output schema, so it should describe the response structure more fully. It mentions a 'paginated JSON array' and pagination metadata, but lacks details about the line item fields. Given the complexity (5 params, 3 required), this is adequate but not thorough.

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 coverage is 100%, so the baseline is 3. The description does not add new meaning beyond the schema; it only repeats parameter names and mentions pagination control. No deeper semantics are provided.

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 'List all line items for a given prime change order,' using a specific verb and resource. However, it later refers to 'enumerate Prime Contracts' which is slightly misleading, as this tool lists line items, not contracts. This minor inconsistency prevents a 5.

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 some usage context, e.g., 'when you need a paginated overview, to find IDs, or to filter by query parameters.' However, it does not specify when not to use this tool or mention alternative sibling tools (e.g., list_prime_contract_line_items), and the phrase 'enumerate Prime Contracts' is imprecise.

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