Show Compliance Information For A Purchase Order Contract

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

The description adds some behavioral context beyond the annotations, such as pagination details and that insurance documents are included. However, the inconsistency regarding 'Commitments' undermines clarity. Annotations already declare readOnlyHint=true, so the read-only nature is clear, but the description could be more accurate.

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 moderately concise but contains redundant and contradictory information. The front-loaded purpose is clear initially, but the later mention of 'Commitments' disrupts flow and could be removed for clarity.

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 the simplicity of the tool (GET with 4 params, no output schema), the description is adequate in covering pagination and required parameters. However, the confusion between compliance and Commitments leaves room for misunderstanding, and it does not fully describe what compliance information is returned beyond insurance.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description does not add significant new meaning beyond restating the required parameters and pagination usage, which is 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 starts by stating it returns compliance and insurance information, but then contradicts itself by saying 'Use this to fetch the full details of a specific Commitments'. This mixing of terms ('compliance' vs 'Commitments') creates confusion and does not clearly identify the tool's specific resource. It also fails to distinguish from the sibling tool for work order contracts.

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?

There is no explicit guidance on when to use this tool versus alternatives like 'show_compliance_information_for_a_work_order_contract'. The instruction to 'Use this to fetch the full details of a specific Commitments' is misleading and does not provide clear usage context.

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