Show Compliance Information For A Work Order Contract

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds pagination details and mentions insurance documents, but incorrectly states it returns 'Commitments' instead of compliance data, slightly reducing transparency.

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 at 5 sentences, but includes redundant information (API path) and a confusing statement about Commitments. Could be streamlined.

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?

Without an output schema, the description should fully explain the response. It mentions paginated JSON with metadata but falsely specifies the content as 'Commitments' instead of compliance data, leaving the agent with incomplete and slightly misleading information.

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?

Input schema has 100% coverage, so the description adds marginal value. It highlights required parameters and pagination controls, but does not explain the meaning of parameters beyond what is 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 states it returns compliance and insurance information for a work order contract, but includes a misleading sentence about fetching 'Commitments' details, which confuses the tool's purpose. It distinguishes from similar tools (e.g., purchase order contract) only by mentioning 'work order contract' in the text.

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 does not provide guidance on when to use this tool versus alternatives like the purchase order contract version. It only restates required parameters without contextual usage advice.

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