Deletes a member tag

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that: the deletion 'changes community state' and mandates confirm=true, which tells the agent this is a state-mutating, confirmation-gated operation.

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, with the core action front-loaded. Slightly over-compressed: the second sentence packages two distinct facts (state change, confirm requirement) and could carry a bit more without bloating.

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 destructive, non-idempotent mutation with no output schema, the description covers the action and the confirm gate but omits whether deletion is permanent, what happens to members currently carrying the tag, and any permission requirements. Adequate but leaves gaps an agent might need before invoking.

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 tag_id, account, and confirm are all documented in the schema itself, including the 'Set true only when the user asked for exactly this action' gloss on confirm. The description's confirm mention restates the schema rather than adding new syntax or format detail, 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+resource ('Deletes a member tag'), which cleanly separates it from siblings create_member_tag, update_member_tag, and list_member_tags. It does not name a sibling or scope the deletion (e.g. whether it detaches the tag from all members) for explicit differentiation.

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 clause 'requires confirm=true for the user-requested action' gives a usable when-to-use hint tied to user intent. However, no alternatives or exclusions are stated (e.g. use untag_member to merely remove a tag from one member), so usage is implied rather than explicit.

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