unsubscribe_from_event

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

Annotations already cover the safety profile (idempotentHint=true, destructiveHint=false, readOnlyHint=false), so the bar is lower. The description adds genuinely useful behavioral context beyond them: the operation only releases registrations owned by this connection or HTTP application, so it cannot affect other connections' subscriptions. It stops short of describing behavior when no matching registration exists.

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?

A single front-loaded sentence with no filler; the scoping constraint that matters most appears immediately.

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?

An output schema exists, so return values need not be explained, and the annotations carry the safety profile. However, the sole parameter is undocumented in both schema and description, and there is no mention of failure behavior when the event is not currently subscribed.

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 single parameter eventName has no description in the schema. The description's phrase 'event registration' only weakly implies the parameter names an event; it gives no format, length, case-sensitivity, or cross-reference to list_available_events for valid values.

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?

States a specific verb ('Release') and resource ('a Firebird event registration'), and the 'owned by this connection or HTTP application' qualifier pins the exact scope. It reads as the clear inverse of the sibling subscribe_to_event, though it never names that sibling explicitly.

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 scope phrase implies this is a teardown/cleanup operation for registrations this connection owns, but there is no explicit when-to-use, when-not, or pointer to subscribe_to_event / list_available_events as the companion tools. Usage is inferable but not stated.

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