eqsl_download

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

With no annotations provided, the description carries the full burden. It discloses the tool's behavior by stating it returns '.adi file content' and instructs to 'save to disk for import into your logger', which adds useful context about output handling. However, it doesn't mention potential side effects, authentication requirements, rate limits, or error conditions that would be important for a download operation.

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 perfectly concise with three sentences that each earn their place: the first states the core purpose, the second explains the return value and usage, and the third provides important guidance about the 'since' parameter. No wasted words, and the most critical information appears first.

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 that there's an output schema (which handles return value documentation) and 100% schema coverage for parameters, the description provides adequate context for this download operation. It explains what the tool does, what it returns, and key usage guidance. The main gap is the lack of behavioral details like authentication or error handling, but with output schema covering return values, this is reasonably 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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds minimal value beyond the schema by mentioning the 'since' parameter's optional nature ('Omit for full history'), but doesn't provide additional semantic context about parameters like 'persona' or 'qth_nickname'. This meets the baseline for high schema coverage.

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 the specific action ('Download your complete eQSL inbox') and the resource ('as raw ADIF text'), distinguishing it from sibling tools like eqsl_inbox (which likely shows inbox contents) and eqsl_ag_check/eqsl_last_upload/eqsl_verify (which perform different eQSL-related actions). The verb 'download' is precise and the output format is explicitly mentioned.

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 ('download your complete eQSL inbox') and includes a specific usage note about omitting 'since' for full history. However, it doesn't explicitly contrast when to use this tool versus its siblings (like eqsl_inbox), which would be needed for a perfect score.

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