Show Prime Change Order Line Item

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds the endpoint method (GET), required parameters, and API version, which is helpful but does not disclose rate limits, authentication needs, or other behavioral aspects beyond what annotations already imply.

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 three sentences: purpose, usage instruction, and required parameters+endpoint. It is fairly concise but has some redundancy (first and second sentence overlap in intent) and a minor typo ('Prime Contracts'). Could be tightened.

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 no output schema, the description mentions it returns a JSON object, but incorrectly specifies 'Prime Contracts' instead of the line item. It does not describe the structure of the return, pagination, or potential errors. The tool's simplicity and annotation coverage partially compensate, but the misnaming 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?

Schema description coverage is 100%, so baseline is 3. The description merely lists the required parameters (company_id, project_id, prime_change_order_id, id) without adding meaning beyond the schema's 'URL path parameter' descriptions. It adds no format, constraints, or relationships.

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 'Get a specified line item for a given prime change order' which is a specific verb+resource. However, it later refers to 'fetch the full details of a specific Prime Contracts' and 'requested Prime Contracts', which is inconsistent (should be Prime Change Order Line Item). This muddles the purpose.

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 Prime Contracts' but provides no guidance on when to use this vs. alternatives among the many sibling show_* tools. It lacks when-not-to-use or alternative tool references.

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