Lotw Download

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context beyond that: it returns .adi file content that should be saved to disk, and large downloads may take 30-60 seconds because LoTW is slow.

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 short, front-loaded with the core action and return format, then adds the key parameter hints and performance warning. Every sentence carries useful information without unnecessary repetition.

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 rich annotations, 100% schema coverage, and existing output schema, the description supplies the remaining practical context an agent needs: raw ADIF output, save-to-disk expectation, QSL filtering behavior, full-history default, and a performance warning. It is complete for correct invocation.

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 all parameters are already documented in the schema. The description reinforces the semantics of qsl_only and since, but mostly repeats schema-level meaning and does not add extra detail for band, mode, or persona.

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 a specific verb and resource: downloading the complete LoTW log as raw ADIF text, and it clarifies the return format as .adi file content. It is clear enough to distinguish this from a general QSO query, but it does not explicitly route the agent away from siblings such as lotw_qsos or lotw_confirmations.

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 gives useful context for saving the raw ADIF file for import into a logger and notes that omitting 'since' returns full history. However, it does not explicitly say when to use this tool versus sibling tools like lotw_qsos or lotw_confirmations, so the usage guidance is implied rather than complete.

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