Check CSV Export Status For Prime Change Order Rows

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

Annotations indicate this is a read-only, idempotent operation. The description adds that it returns a JSON object with file contents or download URL and provides the API endpoint details. It does not contradict annotations and adds useful behavioral context about the response.

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 concise, with a few sentences that front-load the purpose and include necessary details like required parameters. The inclusion of API endpoint info is slightly extraneous but does not significantly detract from clarity.

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 complete input schema and annotations, the description is adequate. It explains the output (downloadable file or URL) and required parameters. However, it lacks detail on pagination behavior or how to handle in-progress exports, leaving some gaps for a complete understanding.

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 with descriptions for all 5 parameters. The description mentions required parameters but does not add additional meaning beyond schema. Baseline 3 is appropriate as schema already covers parameter semantics well.

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 it returns the status of a Prime Change Order Rows CSV export, and specifically mentions retrieving a downloadable file or export URL. It distinguishes from sibling tools (e.g., check_csv_export_status_for_commitment_change_order_rows) by focusing on 'Prime Contracts', making the purpose unambiguous.

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 says 'Use this to retrieve a downloadable file or export URL for Prime Contracts' and lists required parameters. However, it does not explicitly state when not to use this tool or suggest alternatives, such as when using the commitment version instead. The context is clear but lacks exclusions.

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