list_rss_sources

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

With no annotations, the description must fully disclose behavior. It simply says 'List all configured RSS sources' but fails to mention that the active_only parameter defaults to true, meaning not all sources may be returned by default. This is a behavioral nuance that could mislead an agent. No other traits (read-only, pagination, etc.) are disclosed.

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?

A single sentence that is direct and front-loaded. It conveys the core purpose without any filler or redundancy. The structure is clean and efficient.

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?

Despite the tool's simplicity, the absence of an output schema and annotations means the description should explain return values or side effects. It only states the operation but does not describe what the response looks like or any default behaviors. This is insufficient for an agent to fully predict the tool's behavior.

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 coverage is 100%, so the parameters are already described in the input schema. The description adds no additional meaning about the group filter or active_only default. The baseline of 3 is appropriate since the schema handles the parameter documentation.

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 action ('List') and the resource ('configured RSS sources') with a specific context ('web3 news'). It distinguishes itself from sibling tools like add_rss_source or fetch_rss_articles, which perform different operations.

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 the tool is for viewing existing RSS sources, but it does not explicitly state when to use it over alternatives like fetch_rss_articles or get_web3_news. No exclusions or conditional guidance is provided, making it merely implied rather than explicit.

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