get_latest_rss

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

With no annotations, the description carries the burden and discloses key behaviors: default days, maximum limit, optional summary inclusion to save tokens, and behavior for unspecified feeds. It could add edge-case behavior like invalid feed IDs or ordering, but the core read behavior and defaults are well covered.

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 structured with a purpose line, argument list, return type, and examples. It is compact and every section adds information, with no filler.

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 four-optional-parameter read tool with an output schema, the description covers invocation, parameter semantics, examples, and the RSS-vs-news distinction. Combined with the existing output schema, the agent has enough context to select and call the tool 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?

Despite 0% schema description coverage, the description fully documents all four parameters with defaults, max values, example values, and behavioral consequences (e.g., include_summary saves tokens). This adds substantial meaning beyond the bare 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 identifies the tool as fetching the latest RSS subscription data for specified feeds, supports multi-day queries, and explicitly separates RSS from hot-list news, which distinguishes it from sibling get_latest_news. The verb-resource pair is specific and action-oriented.

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?

It explains when to use the tool: for latest content from specific RSS sources, with RSS data separate from hot news. It does not explicitly state exclusions such as 'use search_rss for keyword search', but the context and examples make appropriate use clear.

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