Unsubscribe from events

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

The description states that the tool will 'discard a subscription's buffer', which is a destructive action. However, the annotations set destructiveHint to false, directly contradicting the description. This is a clear annotation contradiction, so the description fails to provide transparent behavioral disclosure.

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 one short, front-loaded sentence with no filler words. It is appropriately concise for a simple operation. However, it is slightly too terse given the lack of parameter and behavioral details, so it does not fully earn its place.

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?

Despite the tool's low complexity (one parameter, no output schema), the description is incomplete due to the annotation contradiction and missing parameter semantics. It does not explain side effects like whether the subscription record itself is deleted, what happens to the buffer, or whether the operation is idempotent. This leaves notable gaps for an agent.

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 0%, and the description does not mention the 'subscription_id' parameter at all. It does not explain what the parameter refers to, its format, or any constraints. With zero coverage, the description must compensate, but it completely ignores the parameter, leaving the agent without guidance on how to populate it.

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 ('stop recording') and the resource ('a subscription's buffer'), distinguishing it from sibling tools like subscribe_events and list_event_subscriptions. The phrase 'discard a subscription's buffer' gives a specific, unambiguous purpose.

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 implies usage context: use this tool to stop recording events and discard the associated buffer. It clearly indicates the action, but it does not explicitly mention alternatives or when not to use it. Since the purpose is obvious from the verb and resource, this is a clear context without exclusions.

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