one_click_unsubscribe

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

With no annotations, the description bears full responsibility for behavioral disclosure. It reveals that the tool only posts to safe HTTPS URLs and only when the List-Unsubscribe-Post header advertises one-click unsubscribe, which is important safety behavior. It does not describe the return value or what happens if conditions are unmet, but the core behavior is transparent.

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 action and a crucial safety qualifier. Every word earns its place, with no redundancy or unnecessary detail.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the action and safety constraints well. However, it does not mention the return value or behavior when the tool cannot perform the unsubscribe (e.g., missing header), which would be useful in the absence of an output schema.

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?

The input schema describes the only parameter (emailId) with 100% coverage: 'The email ID to unsubscribe from'. The description adds no additional parameter semantics beyond what the schema already provides, 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 clearly states the tool unsubscribes from a message using one-click unsubscribe headers, which is a specific verb+resource. It also specifies the scope by mentioning the safety constraint and the List-Unsubscribe-Post condition, distinguishing it from sibling tools like delete_email or archive_email.

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 implies the use case: when you want to unsubscribe from a message via one-click headers. It also provides a clear condition for when the tool will act ('Only posts to safe HTTPS List-Unsubscribe URLs when List-Unsubscribe-Post advertises one-click unsubscribe'), serving as a guideline. It does not explicitly name alternatives, but none exist among the siblings for unsubscribing.

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