unsubscribe

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

No annotations are provided, so the description must disclose behavioral details. It only states that the subscription is closed and returns a dictionary or error message. It does not mention side effects, idempotency, whether other subscribers are affected, or what 'closed' means for subsequent messages—important gaps for a mutable pub/sub 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?

The description is compact and well-structured with a one-sentence purpose, an Args block, and a Returns block. Every sentence earns its place, is front-loaded, and contains no filler or 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?

For a simple one-parameter tool, this description is largely sufficient: it covers the action, the parameter source, and the return type. The existing output schema can handle detailed return fields. It could be more complete by addressing edge cases or idempotency, but that is not critical given the tool's simplicity.

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?

With schema description coverage at 0%, the description compensates by explaining the parameter's provenance: 'The ID returned by subscribe() or psubscribe().' This adds essential meaning beyond the schema's bare 'Subscription Id' and is vital for correct invocation.

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 explicitly states the action with a clear verb and resource: 'Unsubscribe and close an existing pub/sub subscription.' This directly distinguishes it from sibling tools like subscribe, psubscribe, and publish, which are for creating or sending messages.

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 provides clear context by specifying that subscription_id must be 'the ID returned by subscribe() or psubscribe().' This implies the tool should be used only after a subscription has been created, effectively giving prerequisite guidance. It does not enumerate explicit alternatives or exclusions, but for this simple tool the usage context is clear.

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