get_latest_rss

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

No annotations are present, so the description carries full weight. It explains default behaviors (e.g., include_summary saves tokens) and return format, but does not mention potential side effects or rate limits, which are likely minimal.

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 concise and well-structured with a title, explanatory paragraph, Args, Returns, and Examples sections. Every sentence adds value, with no redundancy.

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?

Given the sibling tools and presence of an output schema, the description covers essential context. It notes the data separation from hot news, but could be more explicit about when to use RSS vs other news tools.

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 description coverage is 0%, yet the description fully compensates by explaining each parameter: feeds (list, default all), days (max 30), limit (max 500), include_summary (saves tokens). This provides complete meaning beyond the raw schema.

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 it retrieves latest RSS subscription data and notes its separation from hot news. It implies a distinction from get_latest_news but does not explicitly name alternatives, missing a point for differentiation.

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 provides detailed parameter explanations with defaults and limits, plus examples. It lacks explicit instructions on when not to use this tool or when to prefer siblings, but the context about RSS vs hot news offers implicit guidance.

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