parse_rss_feed

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

No annotations, but description explains it returns feed metadata and up to 20 latest entries with specific fields. Could mention error handling or what happens if feed fails, but acceptable.

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?

Very concise and well-structured: summary, usage advice, then parameter details. No wasted sentences.

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?

Has output schema so return format is covered. Description covers purpose, usage, and parameter. Could add error handling details but not necessary given output schema existence.

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 0% description coverage for the url parameter; description provides full context: the URL of the feed with an example, compensating completely.

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?

Clearly states it parses RSS or Atom XML feeds into JSON with entries. Distinct from all sibling tools, none of which handle feeds.

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?

Explicitly says to use for monitoring news feeds, blog updates, or any RSS/Atom source. Does not mention alternatives or when not to use, but context is sufficient.

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