hamqth_rbn

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

With no annotations, description adds 'public, no auth required' which clarifies access requirements. However, behavioral aspects like data freshness, rate limits, output behavior are not disclosed. Output schema exists but description adds minimal behavioral context.

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?

One sentence, to the point, but overly terse given the number of parameters and potential filtering options. Could provide more structure without being verbose.

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?

Tool has 6 optional parameters and output schema, yet description provides only source and access info. Missing context on default behavior (no params returns all?), typical usage patterns, or how the output is structured. Insufficient for a complete understanding.

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 each parameter has its own description. The tool description does not add additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states tool provides Reverse Beacon Network spots from HamQTH, which differentiates it from sibling DX spots tool. However, it does not explicitly distinguish from hamqth_dx_spots, leaving room for confusion.

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?

Description only mentions that it's public and no auth required. No guidance on when to use vs alternatives like hamqth_dx_spots or other sibling tools. No context on filtering or typical use cases.

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