List Purchase Order Contract Detail Line Items

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds value by specifying it is a GET request, returns a paginated JSON array with pagination metadata, and lists required parameters. This complements the annotations well.

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 (4 sentences) and front-loads the main action. It includes the API endpoint, which may be helpful for debugging but is not essential for an MCP agent. Overall, it is well-structured and to the point.

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?

Despite no output schema, the description clarifies the return format (paginated JSON array) and pagination metadata. It covers required parameters and use cases. However, it does not define what 'Commitments' means in this context, which could be ambiguous. Overall, it is fairly complete for a read-only list operation.

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 parameters are already well-documented. The description only reiterates that page and per_page control pagination and notes required parameters, which adds little beyond the schema. No additional context on filters or parameter interactions is 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?

Clearly states 'List Detail Line Items on a given Purchase Order Contract' and mentions enumeration of Commitments. The verb 'List' is unambiguous, and the resource is specific. However, the term 'Commitments' might cause slight confusion with other line item types, and there is no explicit differentiation from sibling tools like 'list_purchase_order_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?

Provides concrete use cases: 'when you need a paginated overview, to find IDs, or to filter by query parameters.' This helps an agent understand when to invoke the tool. However, it does not mention when not to use it or suggest alternative tools, such as the non-detail line item list.

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