Download Anonymized Trades Archive

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

Annotations already provide hints (readOnlyHint=false, etc.). The description adds valuable behavioral details: file output to output root, CSV format with specific header, 404 handling for weekends/holidays, and that archives are rebuilt nightly. No contradictions.

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 two sentences long. The first sentence states the purpose and output, and the second adds format and error details. Every word is necessary and front-loaded, with no wasted space.

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 CSV structure and error condition (404). It mentions the rebuild schedule, which is helpful. It doesn't detail success behavior but it's implied. Overall complete for a download tool.

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 descriptions for all three parameters. The description adds meaning by specifying the CSV header columns, the file naming convention, and the source of instrumentId. It compensates for any ambiguity in 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 explicitly states the verb 'Download', the resource 'anonymized trades archive', and the context 'for one trading day' and 'into a CSV file'. It distinguishes from the sibling 'download_history_archive' by mentioning 'history-md service' and the focus on trades.

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 clear context for when to use the tool (specific date, instrument) and explains the 404 error meaning. It lacks explicit instructions on when not to use it or alternatives, but the context is sufficient for an agent to decide.

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