List Prime Contract Line Items

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

Annotations declare readOnlyHint=true and destructiveHint=false, confirming safe read operation. The description adds behavioral context: pagination with page/per_page, returns a JSON array, and lists required parameters. No contradictions 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 relatively concise at 5 sentences, covering purpose, usage, pagination, and endpoint. It could be slightly more structured, but all information is front-loaded and relevant.

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 covers key aspects: purpose, required params, pagination, filtering, and endpoint. However, there is a minor inconsistency: it first says 'list of all Line Items' but later says 'enumerate Prime Contracts'. The return format is mentioned as 'paginated JSON array of Prime Contracts' despite listing line items. This ambiguity reduces 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?

Input schema has 100% description coverage, so each parameter is documented. The description adds minimal extra meaning (e.g., pagination control, filters). This meets the baseline, but doesn't significantly enhance beyond schema.

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 all Line Items for the Prime Contract, with specific verb and resource. It distinguishes itself from sibling list tools by focusing on prime contract line items and mentioning pagination and filtering.

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 guidance on when to use the tool (to enumerate Prime Contracts for paginated overview, find IDs, or filter) and references external documentation for filtering. While it doesn't explicitly state when not to use it, the context is clear enough.

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