Update member tag

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 largely covered. The description adds one genuinely useful behavior beyond annotations—the confirm=true requirement—but says nothing about side effects on existing tag membership or the community-state change it alludes to.

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 filler. It is efficient, though the brevity comes at the cost of substance rather than being tightly information-dense.

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 mutation with 13 parameters, nested objects, and no output schema, the description is far too thin. It omits which tag attributes can be changed, the effect on tagged members, and how the payload/payload_file alternatives relate to body flags.

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 only 38% across 13 parameters, and the description only touches confirm=true. The many bare parameters (name, color, emoji, is_public, custom_emoji, display_format, display_locations, is_background_enabled) plus the nested payload object are left undocumented in both places, so the description fails to compensate.

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?

"Update member tag. Changes community state" essentially restates the tool name/title with a generic add-on. It provides no specifics about what a member tag is, what fields are mutable, or how this differs from sibling tools like create_member_tag, delete_member_tag, or get_member_tag.

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 only guidance is "requires confirm=true for the user-requested action," which is an invocation gate rather than a when-to-use signal. There is no indication of when to prefer this over tag_member/untag_member or the other member-tag siblings.

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