Show Purchase Order Contract

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the core behavioral traits are covered. The description adds context about tier-based visibility of change order packages, but does not clarify authentication, rate limits, or other behavioral aspects beyond the annotations.

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 includes a verbose 'Special notes (Tiers)' section that seems misplaced or potentially erroneous (it references 'Work Order Contract' while the tool is for Purchase Order Contract). This adds unnecessary length and potential confusion, detracting from conciseness.

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 should compensate by describing return value structure, but it only states 'Returns a JSON object describing the requested Commitments.' The tiers note provides some context about related data visibility but does not fully explain the response fields.

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% (all parameters have descriptions), so baseline is 3. The description only repeats required parameters already in schema and mentions the endpoint URL, adding no new semantic meaning beyond what the schema provides.

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 the verb ('Return detailed information') and resource ('Purchase Order Contract'), distinguishing it from sibling tools like list_commitments or show_work_order_contract. It specifies exactly what the tool does.

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,' but does not provide guidance on when to use this tool versus alternatives like show_work_order_contract or show_commitment_contract. No explicit when-not-to-use or exclusion criteria.

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