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

The description explicitly states that removing a non-existent tag is a no-op, which adds behavior beyond the idempotentHint annotation. The annotations already cover idempotency and non-destructiveness, but the description reinforces and clarifies this, adding value.

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 two sentences, concise and front-loaded with the primary purpose. It includes the important no-op caveat without extraneous detail. It could be slightly more structured but is 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?

The description covers the core action and the no-op behavior, essential for any lead with or without the tag. However, it does not detail prerequisites (e.g., whether the lead must exist) or any side effects beyond the no-op. The output is likely void, so return format isn't critical. Adequate for a simple tool.

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 already has 100% coverage for all three parameters. The description does not add extra meaning beyond the schema—it simply restates that identifiers can be lead_id or phone_number, which is already in the schema. Baseline 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), the target (a lead), and the identifier options (lead_id or phone_number). It is specific enough to distinguish from sibling 'add_tag' and other lead operations, though it doesn't explicitly name a sibling tool.

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 implies when to use it (removing tags from leads) but does not provide explicit guidance on when not to use it or mention alternatives like 'add_tag'. The no-op behavior for missing tags is a useful usage note but not a full comparison with siblings.

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