rss-feeds-mcp

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

Adds 'configured' (implying persistence) and 'with their categories' (structural hint) beyond annotations, but misses opportunity to clarify return format or pagination behavior.

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?

Single front-loaded sentence with strong verb; no fluff given the tool's simplicity and zero-parameter schema.

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?

Mentions categories which aids understanding, but lacks return value description despite absence of output schema; adequate but not comprehensive for the sibling complexity.

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?

Zero parameters present triggers baseline 4; description appropriately omits parameter discussion as none exist.

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?

Clear verb ('List') and resource ('configured RSS feeds'), with 'configured' effectively distinguishing from fetch siblings, though explicit differentiation from list_categories is absent.

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?

Usage is implied by the listing purpose, but lacks explicit guidance on when to use versus fetch_blogs or list_categories, and omits 'when-not' scenarios.

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