qrz_download

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

With no annotations, the description discloses key behaviors: returns .adi file content, transparently paginates, and is rate-limited. This informs the agent about how the tool operates and potential constraints. Lacks mention of side effects or auth requirements, but these are covered by the required persona parameter.

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 sentences: first states action and output format, second explains usage, third discloses pagination and rate limits. Every sentence adds value, no repetition. Front-loaded with the core purpose.

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?

The description covers output format, pagination, and rate limiting. It does not address error conditions or the role of the 'persona' parameter, but the output schema exists and required parameter is clear. For a relatively straightforward download tool, this is mostly 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 input schema already documents parameters. The tool description adds no extra parameter meaning beyond what is in the schema. For example, 'band' and 'mode' are explained in schema, and description does not clarify default behavior or interaction between filters.

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 tool downloads the complete QRZ logbook as raw ADIF text, using specific verbs and resource. It distinguishes from siblings by emphasizing 'complete' and 'raw ADIF', though no explicit comparison is given.

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?

No guidance on when to use this tool versus alternatives like qrz_logbook_fetch or qrz_logbook_status. The description does not mention use cases, prerequisites, or exclusions, leaving the agent to infer from the name alone.

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