Create PDF Export For A Prime Change Order Batch

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

Annotations already indicate non-destructive behavior. Description adds that it generates an export and returns a download URL or async job handle, which is useful but does not disclose additional behavioral traits beyond what annotations provide.

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 relatively concise (a few sentences) and includes key information. However, it contains a redundant or erroneous sentence about creating Prime Contracts, which slightly reduces efficiency.

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 type (download URL or async job handle) and mentions zone restrictions. It is mostly complete but could elaborate on async job handling or prerequisites.

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% and parameters are clearly described in the schema. The description merely lists required parameters without adding meaning beyond the schema, so it meets the baseline but does not exceed it.

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 creates a PDF export for a Prime Change Order Batch, which is clear and matches the name. However it does not differentiate from sibling tools like create_pdf_export_for_a_prime_change_order or create_pdf_export_for_a_prime_contract.

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?

Includes a note about zone restrictions (US01/US02) and lists required parameters, but lacks explicit guidance on when to use this tool versus alternatives. The incorrect statement 'Use this to create a new Prime Contracts' further confuses usage.

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