lotw_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 performance characteristics ('large logs may take 30-60 seconds') and output format (raw ADIF text). It does not mention authentication or other behavioral traits, but it is transparent about the expected behavior for a download tool.

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 a short paragraph with three sentences. Each sentence serves a clear purpose: stating the action, explaining key parameters, and warning about performance. No unnecessary words.

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 annotations and the parameter count of 5, the description covers purpose, key parameters, performance, and output format. It leaves out details on error handling or required permissions but is sufficient for a download tool. The presence of an output schema reduces the need to explain return values.

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?

Although the input schema has 100% coverage, the description adds useful context: 'Omit 'since' for full history' clarifies the null default, and 'Set qsl_only=True' explains the boolean parameter in plain language. This adds meaning beyond schema field descriptions.

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 verb 'Download' and the resource 'your complete LoTW log as raw ADIF text'. It distinguishes from siblings like lotw_confirmations and lotw_qsos by specifying it returns the full log in ADIF format, which none of the siblings do.

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 specific parameter guidance (e.g., 'Set qsl_only=True for confirmed QSLs only' and 'Omit 'since' for full history') and warns about performance. However, it does not explicitly tell when to use this tool versus alternatives like lotw_qsos or lotw_confirmations.

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