unsubscribe_lead_from_campaign

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Unsubscribe') but does not explain what this entails—whether it's a soft/hard removal, if it affects campaign analytics, requires specific permissions, or has side effects. For a mutation tool with zero annotation coverage, 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, efficient sentence with zero waste. It is front-loaded with the core action and resource, making it easy to parse quickly without unnecessary details.

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 performs a mutation (unsubscribing) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral implications, success/error responses, or integration with sibling tools, which are critical for an agent to use it correctly in context.

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 has 100% description coverage, with clear parameter descriptions ('Campaign ID', 'Lead ID'). The description adds no additional semantic context beyond what the schema provides, such as format examples or relationship details, so it meets the baseline for high schema coverage.

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') and the target ('a lead from a specific campaign'), providing a specific verb+resource combination. However, it does not explicitly distinguish this tool from its sibling 'unsubscribe_lead_globally', which handles global unsubscriptions versus campaign-specific ones.

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 versus alternatives. It does not mention the sibling 'unsubscribe_lead_globally' for global unsubscriptions or other related tools like 'delete_lead_from_campaign', leaving the agent without context for tool selection.

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