Unsubscribe subscriber

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true. The description adds value beyond them by warning that the operation 'may affect delivery, audience membership, published data or irreversible state' – concrete downstream consequences an agent needs before acting – plus the confirm precondition.

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?

Three short sentences with the action, impact warning, and precondition front-loaded in that order. No filler and nothing that could be trimmed without losing meaning.

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 three-parameter mutation with no output schema, the description covers the action, its side effects, and the confirm gate, and the schema covers parameter detail. It stops short of stating reversibility or the expected result, but nothing critical to a correct call is missing.

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 100%, so the schema already documents account, confirm, and subscriber_id thoroughly, including the confirm semantics. The description's only parameter note ('Requires confirm=true') restates what the schema's confirm field says, adding no new format or constraint detail.

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 (Unsubscribe) and resource (subscriber) in the first two words, so the core action is unambiguous. It does not, however, distinguish itself from nearby siblings like delete_subscriber, update_subscriber, or untag_subscriber, which an agent must infer.

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 gives one hard precondition ('Requires confirm=true'), which is real usage guidance, but says nothing about when to choose unsubscribe over delete_subscriber or other subscriber-mutating siblings. Usage is implied by the name rather than explained.

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