Add Member to Access Group

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

Annotations already declare destructive=true, readOnly=false, and idempotent=false, so the safety burden is partly lifted. The description still adds useful context beyond that: it mutates community state and requires an explicit confirm flag, which is the kind of gating detail annotations cannot express.

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, no waste, with the mutation warning and the confirm prerequisite front-loaded. Nothing redundant with 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 six-parameter destructive tool with nested objects and no output schema, the description is thin: it omits the payload/payload_file mutual exclusion, the identify-by-email expectation, and what a successful add returns or whether it is reversible. Adequate but with clear 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 description coverage is 67%, and the schema itself explains confirm, payload, payload_file, and account semantics. The description only echoes the confirm requirement and says nothing about access_group_id (undocumented in the schema) or the id/email binding, so it adds little beyond structured fields.

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 (Add) and resource (Member to Access Group), which is clearly distinguishable from siblings like remove_from_access_group and create_access_group. It does not, however, explicitly name those alternatives to sharpen the distinction.

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 description supplies one real usage rule — confirm=true is required for the user-requested action — which implies a gated-write workflow. It gives no guidance on when to prefer this over create_access_group, add_space_member, or other membership tools.

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