rss-feeds-mcp

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

Annotations fully cover behavior (readOnly, idempotent, openWorld); description adds no new behavioral context but does not contradict 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?

Extremely concise (6 words) but too terse for the complexity of the tool suite; lacks necessary differentiating context despite brevity.

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?

Insufficient given 7 sibling tools with overlapping functionality; fails to clarify the feed/source selection use case despite requiring specific source names.

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 has 100% description coverage with clear parameter semantics; description adds nothing but baseline is 3 per rules for high schema 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?

States basic action (fetch blogs) but 'specific source' is vague and fails to distinguish from sibling 'fetch_blogs' or clarify what constitutes a source.

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 no guidance on when to use this tool versus 'fetch_blogs', 'fetch_by_category', or 'search_blogs'.

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