List Purchase Order Contract Line Items

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

The description adds important context beyond annotations, such as conditional inclusion of Change Event Line Item information based on user permissions. It also notes pagination metadata in the response. This complements the readOnlyHint and idempotentHint 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 structured and efficient, starting with the core purpose, then usage guidance, behavioral notes, and API details. It includes a documentation link but avoids redundancy. The mention of endpoint and method could be condensed, but overall it is concise.

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 completeness because it refers to the return as 'Commitments' while the tool is for line items, which may confuse. There is no output schema, and the description does not detail the structural fields or possible values in the array. Given the complexity of the schema, more information about the response would be beneficial.

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 input schema has 100% coverage, so the description does not need to add much. It mentions required parameters and pagination controls, which are already in the schema but provides a brief overview. No significant new semantics beyond what is already in the parameter descriptions.

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 tool returns a list of Purchase Order Contract Line Items and mentions pagination and filtering. It distinguishes from siblings by specifying it lists line items for a particular contract, but does not explicitly differentiate from other list tools like list_commitment_contract_line_items.

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 explains when to use the tool (for paginated overview, finding IDs, filtering) and provides a link to filtering documentation. However, it does not mention when not to use it or provide alternative tools for specific use cases, such as retrieving a single line item.

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