Create CSV Export For Prime Change Order Rows

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true) indicate a non-read, non-destructive, non-idempotent operation. The description adds value by explaining the output behavior: 'Generates the export and returns a download URL or async job handle', which goes beyond annotations.

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 adequately sized but includes an extraneous and potentially misleading sentence ('Use this to create a new Prime Contracts in Procore') that should be removed. The first sentence and endpoint info are useful, but the extra sentence detracts from 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?

Given the absence of an output schema, the description provides necessary output details (download URL or async job handle) and required parameters. However, it lacks guidance on associated tools (e.g., status check) and the broader workflow context, leaving it moderately 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?

The input schema has 100% coverage for both parameters. The description states 'Required parameters: company_id, project_id' which merely repeats the schema. The endpoint path hint provides some contextual value but does not add 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 states the core purpose of creating a CSV export, but includes a confusing sentence 'Use this to create a new Prime Contracts in Procore' which contradicts the actual functionality and reduces clarity. The verb 'creates' and resource are identified, but the miscue suggests a possible copy-paste error.

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?

No guidance is provided on when to use this tool versus sibling tools like check_csv_export_status_for_prime_change_order_rows or create_csv_export_for_commitment_change_order_rows. The context of usage (e.g., after creating a change order) is implied but not explicit.

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