Show Prime Contract Line Item

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the agent knows this is a safe read operation. The description adds that it returns a JSON object but does not provide additional behavioral context beyond what annotations offer.

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 concise with a few sentences, front-loading the purpose. It includes helpful extras like the Procore API category and endpoint, though this could be seen as slightly verbose for a tool definition.

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?

No output schema is provided, and the description only vaguely says 'Returns a JSON object'. Additionally, the presence of pagination parameters (page, per_page) on a 'show' endpoint is unexplained, leaving ambiguity about their role. This incomplete context undermines the tool's usability.

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 the schema already documents all parameters. The description merely repeats the required parameters and adds a note about URL path parameters, which provides minimal extra value beyond the 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 that the tool returns a specific line item from a prime contract, using verbs like 'Return' and 'fetch'. It distinguishes itself from sibling tools like list and create variants, but the phrasing 'Prime Contracts' (plural) is slightly imprecise for a single line item.

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 implies when to use the tool ('fetch the full details') and lists required parameters, but it does not explicitly state when not to use it or compare it to alternatives such as show_prime_contract_line_item_project or list_prime_contract_line_items.

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