Create 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 covered structurally. The description adds a genuine behavioral constraint beyond the annotations: that the action mutates community state and is gated behind confirm=true tied to an explicit user request. It still omits what state changes occur and whether the tagging is reversible.

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, front-loaded, with no padding. The wording is efficient, though the first sentence contributes almost no information because it merely restates the title.

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 a nested payload object, six parameters, and no output schema, the description is far too thin. It never explains what a member tag is, what member_tag_id refers to, or how account selects credentials, leaving significant gaps.

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 coverage is moderate (67%) and the description explains nothing about the parameters beyond reasserting the confirm gate already documented in the schema. The undocumented top-level user_email and member_tag_id body flags, plus the mutual exclusivity of payload vs. body flags vs. payload_file, are not compensated for in the description.

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 only purpose statement is 'Create Tagged Member,' which repeats the tool name and title verbatim, making it essentially a tautology rather than a description of the member-tag association being created. It gives the agent no way to distinguish this from siblings like create_member_tag, untag_member, or create_space_group_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?

The phrase 'requires confirm=true for the user-requested action' is the only usage signal, and it concerns confirmation rather than when to choose this tool over alternatives. No guidance is offered on when to tag a member versus creating a tag or adding them to a group.

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