Create PDF Export For A Prime Change Order

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate it's a write operation but not destructive. The description adds that it generates an export and returns a download URL or async job handle, which clarifies the async nature. However, it does not disclose potential side effects, authentication requirements, or rate limits. The zone limitation is helpful context.

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 contains 6 sentences, but one sentence ('Use this to create a new Prime Contracts in Procore') appears erroneous and detracts from clarity. The zone note and output description are relevant, but overall it could be more concise and accurate.

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?

For a non-trivial tool (async PDF export with job handling), the description lacks details on how to monitor job status, handle errors, or interpret the output (download URL vs job handle). No output schema is provided. The zone limitation adds some context, but overall completeness is insufficient.

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 3 parameters with descriptions covering 100% of properties. The description only lists them as required without adding semantic meaning beyond the schema. Baseline of 3 is appropriate given full schema coverage.

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 identifies the action ('Creates a PDF export for a given Prime Change Order') and the output ('returns a download URL or async job handle'). However, it does not explicitly differentiate from sibling tools like 'create_pdf_export_for_a_commitment_change_order' or 'create_pdf_export_for_a_prime_change_order_batch', though the singular 'a given Prime Change Order' implies single vs 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 provides a zone limitation (US01 && US02) but offers no guidance on when to use this tool vs alternatives. The statement 'Use this to create a new Prime Contracts in Procore' is confusing and seems erroneous, as the tool creates a PDF export, not a contract. No when-not or alternative tools are mentioned.

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