Delete Tagged Member

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds the confirm gate and 'changes community state', but the confirm semantics are also duplicated in the schema's parameter description, so net added value is modest.

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, front-loaded sentences with no padding. Minor waste in the first sentence restating the title verbatim rather than elaborating.

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?

No output schema exists, so the description need not explain returns, and annotations plus full schema coverage carry most of the burden. However, 'changes community state' is vague about what exactly is destroyed (tag removal vs. member deletion), leaving the agent to infer the effect.

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 parameters (account, confirm, user_email, member_tag_id) are already documented in the schema. The description only gestures at confirm and adds no syntax or format detail beyond what the schema provides; 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?

The description states a verb+resource ('Delete Tagged Member'), but it is a verbatim repetition of the title, so it offers no information beyond the already-visible name/title. It also fails to distinguish this tool from close siblings like tag_member, delete_member_tag, or remove_member.

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 implies usage via 'requires confirm=true for the user-requested action', which is a real prerequisite, but there is no explicit when/when-not guidance and no mention of the alternative tagging tools an agent might confuse this with.

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