get_latest_rss

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

With no annotations provided, the description effectively discloses behavioral traits: it returns JSON, supports parameters like include_summary to save tokens, and imposes limits. It implies a read-only operation and provides examples of usage.

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 well-structured with a title, context, Args, Returns, and Examples sections. It is mostly concise, though the first sentence about storage could be considered slightly extraneous but not detrimental.

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 tool's simplicity (4 params, none required, output schema exists), the description covers purpose, parameters, return format, and examples. It is complete enough for an agent to use correctly, though the 'Returns' is vague but compensated by the output schema.

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 input schema has 0% description coverage, but the tool description includes a detailed Args section explaining each parameter (feeds, days, limit, include_summary), including defaults, maximums, and effects, adding significant value beyond the 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 that the tool retrieves the latest RSS subscription data with multi-day query support. It distinguishes itself from sibling tools like get_latest_news by emphasizing that RSS data is stored separately from hot news.

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 indicates suitability for getting latest content from specific RSS sources but does not explicitly compare with alternatives like search_rss or get_latest_news. Usage guidance is implicit rather than explicit.

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