Create 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 covered. The description adds that the call 'changes community state' and requires confirm=true, which is useful reinforcement but not new depth (confirmation is also documented in the schema).

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 purpose and the confirm constraint front-loaded; no filler. It is appropriately sized, though the extreme brevity is a symptom of under-specification rather than tight writing.

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?

A destructive, non-idempotent mutation with 12 parameters, nested objects, no output schema, and 33% schema coverage warrants far more explanation (required fields, payload vs body-flag mutual exclusion, return behavior). The two-sentence description leaves the agent substantially under-informed.

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?

With 12 parameters and only 33% schema description coverage, the description should compensate but instead omits all parameter semantics. The only param referenced (confirm) is already explained in the schema, so the description adds nothing for name, color, emoji, payload, or the nested display objects.

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 opens with 'Create Member Tag,' which is a verbatim restatement of the tool name and title. It adds no scope, target, or distinguishing detail versus update_member_tag, delete_member_tag, or tag_member, so it functions as a tautology.

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 notes that confirm=true is required 'for the user-requested action,' which is a usage constraint, but gives no guidance on when to use this tool versus sibling tag operations (update/delete/tag_member). No prerequisites or exclusions are stated.

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