search_rss

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

No annotations are provided, so the description carries the full burden. It describes the search operation, return format (JSON list), and parameter constraints (max 30 days). It implies a read-only operation without side effects, but does not explicitly state the lack of destructive actions.

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: a brief purpose line, then Args section, Returns section, and Examples. 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 existence of an output schema, the description appropriately mentions the return format. It covers all parameters, examples, and usage context. No gaps are identified for a search tool.

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%, but the description provides detailed explanations for all 5 parameters, including defaults, constraints (e.g., max 30 days), and examples. This adds significant value beyond the input schema, which only defines types.

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 searches RSS feeds for articles containing a keyword. It specifies the exact resource (RSS data) and action (search), distinguishing it from other tools like get_latest_rss or search_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 provides clear context for when to use the tool (searching RSS data for keyword) and includes examples. However, it does not explicitly mention when not to use it or compare it to alternative sibling tools like search_news or get_latest_rss.

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