Feeds Fetcher List

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

With no annotations provided, the description carries the full behavioral burden, yet it only states that a list is returned. It does not confirm this is a safe read-only operation or mention any side effects, even though it is a fetcher enumeration. An output schema exists so return shape need not be described, but the safety profile is left unstated.

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 front-loaded sentence with no filler or repetition. It is efficient, though the extreme brevity is a byproduct of under-specification rather than deliberate compression.

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 zero-parameter list tool with an output schema, the description is minimally viable but leaves the reader unable to place it among the many sibling list tools. Nothing essential is strictly missing to invoke it, but the lack of any distinguishing context keeps it from being complete.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies, and no parameter-related omissions exist.

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?

Specific verb+resource ("List available feed fetchers") that clearly identifies the operation and the entity being listed. However, it does not distinguish itself from the closely parallel siblings feeds_parser_list, feeds_processor_list, feeds_tamper_list, and feeds_feed_list, which all use near-identical "list" phrasing in the same Feeds namespace.

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 gives no indication of when an agent should call this versus the other Feeds listing tools, nor any prerequisites or context. There is no exclusion or alternative named, leaving routing entirely to inference from the tool name.

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