Qrz Download

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: it transparently paginates internally, it is rate-limited to avoid API bans, and the return value is a .adi file body rather than structured records. The one omission is whether filtering narrows the export or whether the whole logbook always comes back.

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?

Three short sentences, front-loaded with what the tool returns, followed by the actionable instruction and then the behavioral caveats. No boilerplate and every sentence carries information the agent needs.

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?

An output schema exists, so return values need not be spelled out, and all five parameters are documented in schema. What remains missing is the sibling differentiation against qrz_logbook_fetch and any note on how filters affect the exported content, which matters for a tool that otherwise implies an unfiltered full dump.

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%, with band, mode, start_date and end_date each documented inline, so the baseline of 3 applies. The description contributes nothing about the parameters and in fact calls the result a 'complete' logbook, without clarifying how band/mode/date filters interact with that completeness.

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?

States a specific verb and resource: 'Download your complete QRZ logbook as raw ADIF text,' which tells an agent this yields raw file content rather than parsed records. It does not explicitly contrast with the sibling qrz_logbook_fetch, so the agent must infer the difference between a full raw export and a fetch call.

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?

'save to disk for import into your logger' implies the intended downstream use, which nudges toward this tool when a portable file is needed. However, it never names an alternative or states when not to use it, and the presence of qrz_logbook_fetch and qrz_logbook_status in the sibling list makes the choice ambiguous.

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