Untag contacts

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

Without annotations, the description discloses that EntityTag rows are hard-deleted, which is critical behavioral info. It also notes the required environment variables. However, it does not cover error behavior or idempotency.

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 compact (two sentences), front-loaded with the primary purpose, and every sentence adds value without redundancy. Perfectly efficient.

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's low complexity and 100% schema coverage, the description adequately covers purpose, prerequisites, and a key behavioral trait. It does not explain return values or error conditions, but these are partially compensated by the absence of an output schema.

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, so the schema already explains the parameters. The description adds only the environment variable requirement and hard-delete note, which are behavioral rather than parameter-specific. Thus, no significant additional value beyond the schema.

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) and the resource (one or more contacts), making it distinct from the sibling tool 'civicrm_tag_contacts' which adds tags. The verb 'Remove' is specific and unambiguous.

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 indicates when to use this tool (to remove a tag) and mentions prerequisite environment variables. It lacks explicit guidance on when not to use it or alternatives, but the sibling list provides enough context for an AI agent to infer.

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