remove_subscriptions

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

With no annotations, the description carries the burden, and it does disclose the key side effect: the optional purge of stored entries and read state. It also flags a required input form for RSSHub. It leaves default mode behavior and irreversibility unstated, but the disclosed behavior goes well beyond the name and schema.

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?

Two sentences with no filler: the main action is first, the purge option is next, and the important RSSHub feedUrl rule closes the description. Every clause contributes information.

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 two-parameter destructive tool with no annotations and no output schema, the description covers the action, the optional side effect, and a crucial input constraint. Missing specifics are the default behavior of mode=unsubscribe and response/error semantics, but these are modest gaps rather than blockers.

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%, so the description must compensate. It maps the mode parameter to the purge behavior and gives a concrete feedUrls format requirement (stored rsshub://... URLs). It does not spell out both enum options or array limits, but those are either self-evident or contained in the 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 uses a specific imperative verb and resource: 'Remove RSS subscriptions'. It immediately adds the optional purge behavior and the RSSHub feedUrl constraint, making the tool's purpose unmistakable and distinct from sibling upsert/list 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?

It clearly frames when the tool applies (removing subscriptions) and gives an explicit operational rule: 'RSSHub subscriptions must be removed using their stored rsshub://... feedUrl'. It does not name sibling alternatives or give a when-not-to-use statement, so it stops short of a 5.

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