deleteUnsubscribe

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real value beyond them: no soft-delete or undo path via the API, the records are unrecoverable, and the exact return shape ('status: success'). It does not discuss permissions/auth, which keeps it short of a 5.

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?

Front-loaded with the core action and well-sectioned with bold labels. Slight redundancy: 'cannot be undone via API' and 'No soft-delete via API - records removed are not recoverable' say nearly the same thing twice.

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?

No output schema exists, and the description covers the return string, the destructive/irreversible nature, and the consent precondition, so an agent has what it needs to call this correctly. Missing only auth/permission expectations for a destructive operation.

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?

One parameter with 0% schema description coverage, so the description must carry the load. It only restates that 'id' is required and implies it identifies the unsubscribe record; it adds no format, type, or lookup guidance beyond the schema's required array. Baseline credit for a single obvious identifier, but no extra meaning.

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 and resource ('Permanently delete an unsubscribe record by ID') and explicitly distinguishes itself from siblings by naming get/update/deleteUnsubscribe behaviors. An agent can immediately tell this is the hard-delete member of the unsubscribe family.

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?

Gives an explicit use case ('re-subscribing an email address to newsletters and automated email campaigns'), a precondition ('Confirm the recipient's consent first'), and names the alternative ('See also: updateUnsubscribe (modify without removing)'). Routing is unambiguous.

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