feed_unsubscribe

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

Adds behavioral details beyond annotations: removes subscription and dedup history, does not delete existing memory entries, and explains re-subscription behavior. Annotations only give destructive and idempotent hints.

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?

Description is concise and to the point. Includes a brief explanation of consequences and a separate Args section. No wasted words.

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?

Given the tool's simplicity (1 parameter, good annotations, output schema exists), the description fully explains the behavior, including what is removed, what persists, and re-subscription implications.

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 schema already has description 'ID from feed_list()' covering the parameter. The description repeats this in the Args section with slight additional context. With 100% schema coverage, the added value is minimal.

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 'unsubscribe' and the target resource 'feed', and distinguishes it from sibling tools like feed_subscribe and feed_list.

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?

Provides guidance to use feed_list() to find the feed_id, and explains the effect on existing memory entries. However, it does not explicitly state when not to use it or specify alternatives.

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