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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds real context beyond that: keyword normalisation, the 10-term union cap, de-duplication ("each once"), and the provenance distinction between publisher tags and counted phrases. It does not discuss pagination behaviour or rate limits, keeping it short of a 5.

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 core behaviour is front-loaded in the first sentence, followed by normalisation, provenance, and multi-keyword semantics in a logical order. The three spelling variants of "home lab" are illustrative rather than redundant, though the passage is denser than strictly necessary.

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?

With no output schema, the description usefully names the return shape (`topics` for known topics, `unknown` for the rest, plus per-feed provenance). Pagination semantics and the interaction of `limit`/`offset` with the union case are the remaining gap, but an agent has enough to call it correctly.

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 coverage is 100%, so the schema alone would justify a 3, but the description adds genuine meaning for the required `keyword` parameter: normalisation across spellings, phrase tolerance, and comma-separated multi-topic union semantics with the 10-item ceiling. `limit` and `offset` are left entirely to the schema, which is acceptable given the full coverage.

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?

"Every feed filed under one topic" states the resource (feeds) and the filter (topic) concretely, so an agent knows this is a topic-scoped feed listing rather than a post search or a topic catalog. It does not explicitly contrast itself with rssamplifier_list_feeds or rssamplifier_topic_posts, so sibling differentiation is left implicit.

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 tells the agent a keyword can be passed "in any spelling" and that a comma-separated list of up to 10 returns a union, which shapes how to call it. However, it never states when to prefer this over list_feeds or topic_posts, nor any when-not-to-use condition, so usage is implied rather than routed.

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