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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real substance beyond them: the person receives no remaining emails, is permanently barred from re-enrollment, and other campaigns are unaffected. That scoping detail is exactly what an agent needs before committing an irreversible change, though it says nothing about behavior when the enrollment does not exist or about permissions.

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?

Two short sentences, no filler, with the immediate effect front-loaded and the collateral-scope reassurance last. Every clause carries information an agent would otherwise have to guess.

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 one-parameter mutation with no output schema and annotations covering the safety profile, the description supplies the effect, permanence, and blast radius. The only gaps are error/not-found behavior and required permissions, which are minor at this complexity level.

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 single parameter's description already tells the agent where to obtain enrollment_id. The description's 'one person' reinforces the single-enrollment granularity, which is a small addition, but it adds no format or sourcing detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Take one person out of a campaign') with clear scope: a single person, one campaign. It implicitly separates itself from delete_contact via 'Their other campaigns are untouched', but it never names an explicit alternative such as unsubscribe_email or delete_campaign, so the sibling differentiation is only partial.

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?

Usage is implied rather than stated: 'now' signals immediacy and 'never join it again' signals permanence, which helps an agent judge when this is appropriate. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives like unsubscribing or pausing, so the agent must infer the boundary itself.

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