get_latest_rss

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

With no annotations, the description carries the burden of behavioral disclosure. It explains key behaviors like defaulting to all feeds when none specified, days max of 30, limit max of 500, and include_summary defaulting to False. It also states the return format. However, it omits any error behavior, authentication requirements, or rate limits, leaving some transparency gaps.

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: a brief purpose statement, an Args section with bullet points, a Returns line, and examples. It is front-loaded with the main purpose and avoids unnecessary fluff. It could be slightly more concise, but the organization aids comprehension.

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 has 4 optional parameters and a simple retrieval purpose, the description covers all parameter semantics, provides examples, and states the output format. It does not mention error conditions or edge cases, but the presence of an output schema and the simplicity of the operation mean the essential context is present for an agent to use it correctly.

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 description goes well beyond the bare schema, which has no parameter descriptions. The Args section clearly explains each parameter: feeds (list of IDs, all if not set), days (default 1, max 30), limit (default 50, max 500), and include_summary (default False, token saving). This strongly compensates for the 0% schema coverage and adds critical semantic meaning.

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 fetches the latest RSS subscription data and supports multi-day queries. It differentiates RSS from hot-list news by noting they are stored separately, which helps distinguish it from sibling tools like get_latest_news and get_trending_topics, though it does not name them explicitly.

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 when to use this tool: for retrieving RSS content from specific sources, as opposed to hot-list news. It provides examples of different call patterns, but does not explicitly name alternative tools or state conditions under which to prefer this one over a sibling. The guidance is implicit rather than directive.

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