deleteUnsubscribe

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

Adds key behavioral details beyond annotations: 'Permanently delete', 'cannot be undone via API', 'No soft-delete via API - records removed are not recoverable.' Consistent with destructiveHint=true. No contradiction with idempotentHint=true (delete is idempotent).

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?

Well-structured with clear sections: summary, use case, required param, alternatives, destructive warning, return format. Every sentence adds value, and key points are front-loaded. No filler.

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 tool with one parameter and no output schema, the description covers purpose, usage context, behavioral traits, and return value. Annotations are present, and the description complements them well, addressing consent and bulk use concerns.

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?

Only parameter is 'id', and schema description coverage is 0%. The description merely repeats 'Required: id.' without explaining what the id represents or any constraints. Given low coverage, additional param context is needed but missing.

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 'Remove email from unsubscribe list - Permanently delete a unsubscribe record by ID.' The verb 'delete' matches the tool name, and it specifies the resource (unsubscribe record), distinguishing it from other delete tools like deleteClick or deleteForm.

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?

Explicit usage guidance: 'Use when: re-subscribing a member (remove their unsubscribe entry).' Warns against misuse: 'Confirm the member's consent first - don't use to silently re-enable emails.' Provides alternative: 'See also: updateUnsubscribe (modify without removing).' Adds caution for bulk use.

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