rss-feeds-mcp

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

Adds scope context ('across all feeds') beyond annotations, though omits return format details and rate limiting since annotations cover safety/read-only traits.

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 well-structured sentence with purpose front-loaded and benefit clause appended; no fluff but could use punctuation to separate clauses.

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?

Adequate for basic invocation but lacks description of return values since no output schema exists (only hint is 'content ideas' and schema's 'articles' reference).

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% with clear examples; description relies on schema without adding redundant parameter guidance, meeting baseline.

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 ('Search') + resource ('blogs across all feeds') with explicit keyword mechanism that distinguishes from fetch-by-category or list operations.

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 one use case ('finding content ideas') but lacks explicit when-not-to-use guidance or comparison to fetch_blogs/fetch_from_source alternatives.

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