Show Purchase Order Contract Line Item

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

Annotations already provide readOnlyHint=true and idempotentHint=true, describing safety. The description adds that change event line item info is conditionally returned, but does not cover other behavioral traits such as auth needs, rate limits, or full return format.

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 has five sentences, including redundant statements like 'Return a Purchase Order Contract Line Item' and 'Returns a JSON object describing the requested Commitments.' It could be more concise by merging the initial and later return statements.

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 there is no output schema, the description should explain what attributes are in the returned JSON object. It only says 'Returns a JSON object describing the requested Commitments,' which is vague. The tool's complexity and lack of output details reduce 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 input schema has 100% description coverage, so all six parameters are already documented. The description merely lists the three required parameters without adding new semantics or usage context.

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 it returns a Purchase Order Contract Line Item, provides the verb 'fetch full details', and distinguishes from sibling list tools. However, it refers to 'Commitments' instead of line items, causing minor confusion.

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 fetch the full details of a specific Commitments by its identifier,' implying when to use it, but does not explicitly state when not to use it or provide alternatives among siblings like list_purchase_order_contract_line_items.

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