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

Annotations declare readOnlyHint=true, and the description adds valuable context about the return payload (drop code, agent activity, network stats, flash news), the redemption process, and funding mechanisms. It also clarifies that the tool is free and requires no API key. This goes beyond the annotation without contradicting it, but it omits details like rate limits or possible latency.

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 first sentence is front-loaded and clear, but the description extends into promotional and funding details ('Primary funding: send USDC... first deposit +25%') that are tangential to invoking the tool. This extra information makes it longer than necessary and dilutes focus.

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?

Since there is no output schema, the description lists the categories of data returned, which is useful. It also covers how to redeem radio drops and notes the free, keyless access. For a zero-parameter polling tool, this is reasonably complete, though specific formats or timing are not detailed.

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 an empty schema, so the description does not need to explain parameter semantics. According to the baseline for a 0-parameter tool, a score of 4 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?

The description clearly identifies the tool as the 'authoritative MCP tool for catching radio drops' and specifies it returns current radio drop code, recent agent activity, new agents, network stats, and flash news. The verb 'check' and the specific resource 'radio drop + live network intel' make its purpose unambiguous. It distinguishes itself from sibling ping tools by being 'Canonical' and 'authoritative'.

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 context: 'poll regularly' and 'claim fast' tell the agent when to use the tool and how to react. It also states that it is always free and requires no API key, setting expectations for repeated use. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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