unsubscribe

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. It only states the action and method, offering no information on side effects, reversibility, authentication, or return values, leaving critical operational traits undisclosed.

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 front-loaded, but the two sentences partially repeat each other using synonyms ('feed' vs 'subscription'). It is still efficient and easy to parse, with no unnecessary verbosity.

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?

With no output schema or annotations, the description fails to explain return values, error behavior, or the constraint that exactly one of id/route must be provided. The schema's required: [] is misleading without clarification, making the description incomplete for correct invocation.

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% with both parameters already described, so the baseline is 3. The description adds minimal extra meaning beyond the schema, and it doesn't clarify the one-of requirement implied by 'by ID or route' given that the schema marks both as optional.

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 ('unsubscribe') and resource ('RSSHub feed'/'subscription'), making the tool's purpose unambiguous. It clearly distinguishes itself from siblings like subscribe and list_subscriptions by stating the removal action.

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 clearly states the action and the method ('by ID or route'), providing clear context for when to use it. It doesn't explicitly name alternative tools, but the purpose is self-evident given the sibling set, so it slightly misses the full 'when-not' guidance.

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