Show Compliance Documents For A Contract.

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

Annotations already indicate read-only and idempotent behavior. The description adds pagination details (page, per_page, metadata) and the API endpoint. The misleading 'Commitments' reference is a minor inconsistency.

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 reasonably structured but contains redundant or confusing wording (e.g., 'Use this to fetch the full details of a specific Commitments by its identifier'). Could be more concise.

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 fully explain the return value. It mentions paginated JSON array but incorrectly calls it 'Commitments' instead of compliance documents. Missing details on array structure. Adequate but not fully complete.

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%. The description adds context about required parameters and pagination control beyond the schema. It explains the return format includes pagination metadata, which compensates for lack of output 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 compliance documents for a contract, specifies the verb, resource, and pagination. However, it contains a confusing sentence about fetching 'Commitments' which suggests a copy-paste error, slightly reducing clarity.

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 provides required parameters and pagination instructions but does not explicitly distinguish this tool from siblings or state when not to use it. No alternatives are mentioned.

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