Show Work Order Contract Detail Line Item

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's mention of 'GET' endpoint and 'Returns a JSON object' adds minimal behavioral context beyond the structured data. No additional traits like rate limits or authentication needs are disclosed.

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, each adding unique value: purpose, usage, and required parameters with endpoint info. It is efficiently packed and front-loaded, with no wasted words.

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 the core purpose and required parameters but lacks details about optional parameters (page, per_page) and the response structure beyond 'JSON object.' Since there is no output schema, additional context on response fields would improve 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 lists the three required parameters (work_order_contract_id, id, project_id) but does not add meaning beyond what the schema already provides (e.g., URL path vs query string distinctions are already in 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 it returns a detail line item for a work order contract. The verb 'Return' and resource 'Detail Line Item' are specific. However, it does not distinguish itself from sibling tools like 'show_work_order_contract_line_item' or 'show_purchase_order_contract_detail_line_item', missing an opportunity for differentiation.

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 Commitments by its identifier,' which implies usage for retrieving detailed information. However, it provides no guidance on when to prefer this tool over alternatives (e.g., listing tools) or any exclusions, leaving the agent to infer context.

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