cm_unsubscribe_subscriber

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

Annotations provide no hints (no readOnlyHint or destructiveHint). The description implies a state change ('Unsubscribe') but does not clarify if the action is reversible, triggers notifications, or has side effects. More behavioral context is needed.

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 one concise sentence with no unnecessary words. It front-loads the key action and resource efficiently.

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 mutation tool with no output schema and minimal annotations, the description is adequate but lacks depth. It does not explain what happens after unsubscription (e.g., confirmation, data retention) or any prerequisites.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's own descriptions for listId and EmailAddress. No additional semantics or constraints are provided.

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 action (Unsubscribe), the target (an active subscriber), and the context (from a list). It is specific and distinguishes from siblings like cm_delete_subscriber or cm_get_unsubscribed_subscribers.

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 provides no guidance on when to use this tool vs alternatives (e.g., cm_delete_subscriber, cm_suppress_emails). It lacks context for prerequisites or scenarios where this is appropriate.

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