Create PDF Export For A Commitment Change Order Batch

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

The description includes a clear behavioral contradiction by stating 'Use this to create a new Commitments,' which is not the tool's function. Annotations do not indicate creation of commitments. The description fails to accurately describe the tool's core behavior, misleading the agent. The zones note is relevant but cannot compensate for the erroneous statement.

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 includes an unnecessary and misleading sentence ('Use this to create a new Commitments') that inflates the word count and harms clarity. The structure is adequate with the zones note and endpoint info, but the error reduces overall 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?

No output schema is provided, so the description should fully explain the return value. It mentions a download URL or async job handle but does not clarify when each is returned or how to handle the async job. Additionally, it omits details about whether repeated calls generate new exports or overwrite existing ones. The misleading commitment creation statement further detracts from 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%, so the schema already describes each parameter well. The description merely lists the required parameters without adding new semantic meaning, such as formats, constraints, or relationships. Baseline 3 is appropriate as the description adds no extra value beyond rephrasing schema information.

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 action 'Creates a PDF export' and specifies the resource 'Commitment Change Order Batch'. It also mentions the output (download URL or async job handle). The tool name and title are descriptive, and it distinguishes from siblings like 'create_pdf_export_for_a_commitment_change_order' (singular) and 'create_pdf_export_for_a_prime_change_order_batch'.

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 restriction (US01 and US02), which is helpful, but it also contains a misleading statement: 'Use this to create a new Commitments in Procore.' This is incorrect and could confuse an agent about when to use the tool. No guidance is provided on when to use this tool versus similar tools for creating PDFs of individual change orders or prime batches.

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