wspr_band_activity

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

No annotations provided, so description carries full burden. It clearly describes a read-only summary operation with no side effects. Could mention data source or limits, but the behavior is transparent enough for safe invocation.

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?

Two short sentences: purpose statement, list of outputs, and a usage hint. No redundant words, front-loaded with key information. Excellent conciseness.

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 one parameter and an output schema (not shown but exists), description lists all output fields (spot counts, station counts, distance, SNR). Adequate for an agent to understand expected results without needing the output schema.

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?

Single parameter 'hours' with 100% schema description coverage (time window, range, default). Description does not add extra meaning beyond what the schema provides, so score is baseline 3.

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 explicitly states 'Get per-band WSPR activity summary' with specific details (spot counts, station counts, distance, SNR). The closing sentence 'best indicator of which bands are open right now' distinguishes it from sibling tools like wspr_grid_activity or wspr_longest_paths.

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?

Provides clear context: 'best indicator of which bands are open right now' implies when to use. However, no explicit guidance on when not to use or alternatives among siblings. Still, the description helps an agent decide.

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