Remove a contact from a tag

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

Beyond the destructiveHint annotation, the description clarifies the actual scope of harm—'Neither the tag nor the contact is deleted'—and reveals the timing behavior 'applied immediately rather than queued'. This is meaningful context that directly prevents an agent from assuming this endpoint deletes either entity.

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 three sentences with no filler: main action first, timing contrast second, non-deletion safety note last. It does not duplicate schema field names or annotation values.

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 mutation with three required UUIDs, annotations for idempotency/destructiveness, and no output schema, the description covers the key operational facts: scope, immediacy, and non-destructive nature to the tag/contact. Nothing essential is missing.

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 the baseline applies; the param entries are terse ('Tag uuid parameter') but unambiguous. The description's 'single contact' reinforces contactUuid semantics but adds no material parameter detail.

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 specific action—'Remove a tag from a single contact'—and names the target resources. It explicitly contrasts itself with the bulk endpoint, making differentiation from reach_removeContactsFromATagV1 and related tag/contact siblings immediate.

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?

It identifies the bulk endpoint as the main alternative and highlights the deciding factor: immediate application vs queued. It does not spell out an explicit 'use this when... / use bulk when...' rule, but the single-contact framing plus timing contrast provides clear context.

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