freshrss_subscribe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Subscribe to a new feed' only implies a state change; it does not mention auth requirements, duplicate handling, folder creation, failure behavior, or other side effects.

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 a single front-loaded sentence with no filler, making it easy to parse. It is concise rather than incomplete to the point of being tautological, unlike a bare 'Process' description.

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 simple one-action tool with a well-defined schema and an output schema, the description is minimally viable. However, without annotations it still leaves gaps around authentication, duplicate subscriptions, and what happens on failure.

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% and the description adds no parameter-level detail beyond the word 'feed.' The schema itself documents feed_url, title, and folder clearly, but the description does not compensate for the low coverage or clarify how these parameters interact.

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 uses a specific verb ('Subscribe') and a resource ('a new feed'), making the intended action clear and distinguishable from sibling operations like freshrss_unsubscribe and freshrss_list_subscriptions. It does not elaborate on the feed format or subscription details, but the core purpose is unambiguous.

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 intended use case is implied by the description: call when the user wants to add a new feed subscription. However, there is no explicit guidance about when not to use it, prerequisites such as authentication, or alternatives among the listed sibling tools.

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