List Prime Contract Line Items

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

Annotations already indicate this is a read-only, idempotent operation. The description adds that it returns a paginated JSON array and includes pagination metadata, but it incorrectly states the returned resource (Prime Contracts instead of line items) and falsely claims filtering via 'query parameters' beyond pagination. This misrepresentation of behavior is a significant gap.

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 verbose and includes redundant information (API version, endpoint path). The contradictory statements (line items vs. Prime Contracts) add confusion. It could be condensed to a few clear sentences without loss of information.

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?

While the description covers pagination and required parameters, it fails to accurately describe the output (line items, not Prime Contracts). Given no output schema, the description carries the burden of explaining the return structure, but it is incorrect. Additionally, the misleading reference to 'enumerate Prime Contracts' and filtering overpromises.

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% with all five parameters described. The description reiterates required parameters and pagination controls but adds no new meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 starts correctly by stating 'List all line items for a given prime contract,' but then immediately contradicts by saying 'Use this to enumerate Prime Contracts' and 'Returns a paginated JSON array of Prime Contracts.' This confusion between line items and contracts undermines clarity. The purpose is partially clear from the first sentence, but the misleading subsequent statements lower the score.

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 offers vague usage guidance ('Use this to enumerate Prime Contracts when you need a paginated overview, to find IDs, or to filter by query parameters'), but it does not differentiate this tool from siblings like list_prime_contracts or other line item tools. No explicit when-not or alternative recommendations are provided, making it difficult for an agent to decide when to use this tool.

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