sendcraft_unsubscribe

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

No annotations are present, so the description must fully disclose behavior. It states the core action and scope but omits whether the action is reversible, what happens to scheduled emails, or whether it affects transactional email. Additionally, conflating unsubscribe with GDPR deletion is misleading. The description lacks the behavioral detail expected for a mutation tool.

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 two sentences, front-loaded with the primary purpose, and contains no redundant or tangential information. It is efficiently structured and highly scannable.

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 tool with a single parameter and no output schema, the description covers purpose and usage well. The slight GDPR inaccuracy and lack of side-effect details prevent a perfect score, but the description is largely complete for 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?

Schema coverage is 100% and the parameter 'email' is clearly described as the target address. The tool description adds no extra parameter detail beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Unsubscribe') and clearly identifies the resource ('a contact') and scope ('from all marketing emails'). This effectively distinguishes the tool from email-sending and campaign tools, and the action is unambiguous.

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 'Use when' guidance is provided with two concrete scenarios. However, the mention of 'GDPR deletion requests' is potentially misleading because unsubscribing is not equivalent to data deletion; this prevents a perfect score.

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