fetch_rss

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

The description discloses the return fields and the filter behavior, but it references a 'filter_out_topics' parameter that does not exist in the schema, which is misleading. There are no annotations to support the safety profile, and the description does not address potential errors or formatting.

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 description is two sentences and front-loaded with the core purpose. However, the second sentence introduces inaccurate parameter information, which undermines its value.

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?

For a simple tool with no annotations or output schema, the description should explain parameters and edge cases. It fails to describe 'limit', references a non-existent parameter, and lacks alternatives or error handling, leaving an agent with incomplete information.

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?

The schema has two parameters (url, limit), but the description only mentions a phantom 'filter_out_topics' parameter and provides no meaning for 'limit' or 'url'. This does not help an agent understand the actual parameters.

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?

The description clearly states the tool fetches any RSS feed by URL, which is a specific verb+resource. It distinguishes itself from specialized feed tools like get_tech_feed by emphasizing 'any RSS feed'.

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 implies a general-purpose use case ('any RSS feed') but does not explicitly mention when to use this over siblings. No exclusions or alternatives are named, so guidance is merely implied.

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