reach_removeAContactFromATagV1

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

With no annotations, the description carries the full burden of behavioral disclosure. It provides two key traits: immediate execution (not queued) and non-destructive behavior (neither tag nor contact is deleted). This meaningfully informs the agent about side effects and timing. However, it omits details like idempotency, error conditions, or required 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?

The description is exactly two sentences: the first states the core action, the second provides important caveats (immediate vs queued, non-deletion). Every sentence earns its place with no wasted words.

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 simple operation, three well-schema'd parameters, and no output schema, the description adequately covers purpose, usage distinction, and side effects. It is sufficient for an agent to select and invoke the tool correctly, though it could mention return behavior or prerequisite conditions.

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%, but each parameter description is minimal ('Tag uuid parameter', etc.) and adds little beyond the parameter name. The tool description offers no additional parameter semantics, so the baseline of 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 clearly states the action: 'Remove a tag from a single contact.' This is a specific verb+resource+scope combination. It also distinguishes itself from the bulk endpoint by emphasizing 'single contact' and from tag deletion by clarifying 'Neither the tag nor the contact is deleted.'

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 explicitly contrasts with the bulk endpoint: 'Unlike the bulk endpoint this is applied immediately rather than queued.' This tells the agent when to prefer this tool (immediate application for a single contact) over the bulk alternative, though it does not name the alternative explicitly or provide comprehensive when-not-to-use guidance.

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