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

With no annotations, the description carries the behavioral disclosure burden. It does add some useful traits—public web scope, RSS-based search surface, and no API-key requirement—but it omits any mention of return format, pagination, rate limits, or limitations. This is a minimal but non-empty disclosure.

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 a single, front-loaded sentence with no filler. Every word serves a purpose, though the 'No paid API key' clause is a peripheral benefit statement rather than core behavior.

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 tool has no output schema and no annotations, so the description must carry more explanatory weight. It fails to mention what results look like, how the limit affects output, or any operational caveats, making it incomplete for confidently invoking 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?

Schema description coverage is 0%, and the description provides no meaning for the 'query' or 'limit' parameters beyond what the property names imply. For two parameters that are entirely undocumented, this is a significant gap that the description should have compensated for.

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 action ('Search the public web') and the mechanism ('free RSS search surface'), which is specific enough to convey the tool's core purpose. It does not explicitly differentiate from sibling tools like neo_discover, but the RSS and free-web framing makes the resource and scope reasonably clear.

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 offers no guidance on when to choose this tool over alternatives or when not to use it. The phrase 'No paid API key' hints at a cost advantage but does not explain context, prerequisites, or boundaries such as preferring neo_discover for other search needs.

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