Create CSV Export For Commitment Change Order Rows

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

The description adds value by noting the tool generates a download URL or async job handle. Annotations provide readOnlyHint=false, but the description does not contradict. However, the erroneous 'create a new Commitments' statement undermines trust.

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?

Multiple sentences, but the second sentence is a misleading filler. The rest (endpoint, async info) is useful. Could be shorter and more focused.

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?

The description mentions the async job handle and download URL, which is helpful given no output schema. However, it does not link to the status check tool or explain how to handle the async response.

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 clear descriptions for both parameters. The description merely restates required parameters without adding new semantic information like formats or examples.

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 CSV export for the Commitment Change Order Rows collection, which is clear. However, the misleading sentence 'Use this to create a new Commitments in Procore' introduces confusion about the tool's actual purpose, reducing 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?

No guidance on when to use this tool versus alternatives like 'check_csv_export_status_for_commitment_change_order_rows'. The description lacks context for selecting this tool among siblings.

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