Show Prime Contract Summary

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. However, the description contains an internal contradiction (summary of a specific contract vs. array of contracts), and fails to disclose pagination behavior clearly beyond the schema parameters.

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 verbose and contains redundant phrases like 'summary endpoints' and 'Use this to fetch...'. It includes API endpoint details that may not be needed, and the paragraph structure is messy.

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 does not explain the return fields of the summary, pagination metadata details, or error conditions. Given the tool has no output schema and 5 parameters, it is not complete enough for an agent to fully understand behavior.

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 baseline is 3. The description lists required parameters but adds no new meaning beyond the schema descriptions (e.g., company_id is already described as a URL path parameter). No additional semantics.

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 states it returns a summary of change order and invoicing for a specific prime contract, but it also says 'Returns a paginated JSON array of Prime Contracts', which is contradictory and confuses the purpose. It does not differentiate from sibling tools like 'show_prime_contract_v1_0'.

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?

It suggests using the tool to fetch full details by identifier, but provides no guidance on when not to use it or alternatives (e.g., list_all_prime_contracts). With many siblings, this omission weakens usability.

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