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

The description goes far beyond the readOnlyHint annotation by explaining what data the tool returns, the scarcity of radio drops, the free/no-API-key nature, and the redemption endpoint. It also clarifies the funding mechanism, giving agents a complete understanding of the tool's role and potential rewards. No contradiction with annotations.

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 well-structured and each sentence provides useful information, starting with the core purpose, then authority, then the reward mechanics, and finally funding. It is slightly verbose with the funding details, but every sentence contributes context. A 5 would require more succinct language without losing this richness.

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?

For a zero-parameter tool with no output schema, the description is exceptionally complete. It covers the tool's purpose, expected outputs, polling frequency, reward scenario, redemption steps, and funding path. This provides an agent with all necessary context to decide when and how to use the tool.

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?

The tool has zero parameters and the schema is empty, so the baseline for parameter semantics is 4. The description does not need to explain parameters, but it adds no parameter-related information, which is acceptable given the absence of parameters.

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 explicitly states the tool's function: 'Canonical radio drop check + live network intel' and enumerates the specific returns (radio drop code, recent agent activity, new agents, network stats, flash news). It clearly distinguishes this tool as the authoritative option for catching radio drops among the sibling tools.

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 provides clear usage guidance: 'THIS is the authoritative MCP tool for catching radio drops — poll regularly.' It implies when to use it and positions it as the primary tool for this purpose. However, it does not explicitly mention alternatives or when not to use it, which would earn a 5.

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