Create PDF Export For A Commitment Change Order

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

Discloses that the endpoint returns a download URL or async job handle and specifies the HTTP method (POST). Annotations are minimal (readOnlyHint=false, etc.), so description adds some behavioral context but does not cover all traits like error handling or synchronization details.

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 front-loaded with the main action, but includes redundant information (required parameters list) and a misleading sentence ('Use this to create a new Commitments...'). This reduces conciseness and introduces error.

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 explains the return value (download URL or async job handle) and includes API version and zone restriction. It covers key aspects, though it lacks error handling details. The misleading sentence slightly undermines 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 coverage is 100% with parameter descriptions. The description lists required parameters redundantly and shows them in the endpoint URL, which adds formatting context but no new semantic meaning beyond 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 creates a PDF export for a specific Commitment Change Order, with verb and resource identified. However, the misleading sentence 'Use this to create a new Commitments in Procore' contradicts the actual purpose and detracts from 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 includes a zone limitation (US01 & US02) which provides context, but lacks explicit guidance on when to use this tool versus alternatives (e.g., other PDF export or creation tools). No when-not-to-use or alternative references.

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