feed_unsubscribe

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

Discloses removal of subscription and dedup history, clarifies memory entries are not deleted, and warns about re-ingestion on re-subscription. No annotations provided, so description carries full burden.

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?

Multiple sentences each add valuable information: action, side effects, warning, and usage hint. No redundancy or fluff.

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?

Covers behavior, side effects, dependency on feed_list, and re-subscription implications. Has output schema (context signal), but description suffices without needing to explain return values.

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 100%; description repeats schema's parameter description without adding new meaning. Baseline 3 applies.

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?

Description clearly states 'Unsubscribe from a feed and stop future polling.' Uses specific verb (unsubscribe) and resource (feed), and distinguishes from siblings like feed_subscribe.

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?

Explicitly instructs to use feed_list() to find the feed_id, implying prerequisite. Does not explicitly state when not to use, but context of sibling tools provides differentiation.

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