Unsubscribe from Feed

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

With no annotations, the description discloses non-destructive behavior: it only removes the user's subscription, does not affect team members or catalog, and preserves bookmarks. This provides sufficient transparency for a safe operation.

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 concise sentences, front-loaded with the main purpose. Every sentence adds value without redundancy.

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 simple single-parameter tool with no output schema, the description covers all necessary context: what it does, what it doesn't affect, and side effects on bookmarks.

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 covers 100% of parameters with a description for 'feed_id'. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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 verb 'Unsubscribe', the resource 'feed', and specifies the scope: 'Only removes your subscription'. It distinguishes from siblings like 'remove_bookmark' or 'remove_playbook'.

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 clarifies when to use this tool: to unsubscribe without affecting others or the shared catalog, and that bookmarks are preserved. It implies when not to use (e.g., to delete the feed entirely).

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