Unsubscribe from a conference

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds valuable behavioral context beyond annotations, specifically that the cursor is discarded and resubscribing starts fresh. This is useful for an agent to understand side effects.

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 three sentences long, with the first sentence stating the purpose, the second providing usage guidance, and the third clarifying a behavioral consequence. No unnecessary 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?

For a simple one-parameter tool that likely returns a standard result (output schema exists), the description covers the needed information: when to use, how to get the parameter, and what happens upon use. It is complete enough for an agent to invoke correctly.

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 0%, so description must explain the parameter. It does so by directing the agent to 'Pass the subscription_id from list_subscriptions', which adds practical context beyond the schema's type and minLength constraint.

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 specific verbs ('stop following', 'unsubscribe', 'drop') and the resource ('conference'), and distinguishes it from the sibling tool 'subscribe_conference' and other subscription-related tools.

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 explicitly states when to use this tool ('when the user asks to stop following / unsubscribe / drop a conference') and provides a crucial prerequisite: pass the subscription_id from list_subscriptions. It also clarifies the consequence of use (cursor discarded).

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