customerthermometer_unsubscribe_recipient

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

With no annotations, the description must carry the behavioral disclosure burden. It reveals that the tool adds to an unsubscribe list, implying a mutating action, but it does not state whether the action is reversible, whether it requires special permissions, or what effect it has on future sends. For a write operation, this is a significant gap.

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 a single front-loaded sentence with no redundant words or filler. Every word contributes to identifying the action and target list.

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 2-parameter tool with full schema coverage, the description plus schema is minimally adequate to make a correct call. However, there is no output schema and no mention of side effects, return behavior, or when to choose this over the similar add_recipient_to_list sibling, leaving clear gaps.

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 schema already covers both parameters with 100% coverage: emailAddress is described as the email to unsubscribe and notify as whether to notify the account. The description adds no new parameter-level detail, so the baseline 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 states a clear action ('Add an email address') and a specific resource ('the account's Customer Thermometer unsubscribe list'), so an agent can infer the tool unsubscribes an email. It does not explicitly contrast with the similar sibling customerthermometer_add_recipient_to_list, but naming the unsubscribe list provides enough differentiation.

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 no guidance on when to use this tool instead of a sibling, nor any prerequisites or exclusions. The only usage signal is the tool name and the action itself, which is not enough to route an agent among add_recipient_to_list and other list-related tools.

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