add_member

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top of that: it does not say what happens on a duplicate add (non-idempotency matters here), what permissions are required, or what errors can occur.

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?

The description is a single short phrase, so it is front-loaded and free of bloat. It is arguably too terse for its job, but conciseness itself is not the problem.

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?

This is a mutating membership operation with no output schema and only 2 parameters; a correct invocation depends on knowing prerequisites (member exists in workspace, caller has group-admin rights), duplicate behavior, and failure modes, none of which are stated. For a non-idempotent mutation the description is under-specified.

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%, with both group_id and email documented in the schema, so the baseline is 3. The description contributes no additional meaning about the parameters (e.g., whether email must be an existing workspace member), but nothing is missing from the structured data.

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 gives a verb+resource ('Add Member To User Group'), which clarifies that the resource is user-group membership rather than, say, a project or workspace invite. However, it is nearly a verbatim restatement of the tool name and title, adding little beyond the group scoping detail, and it does not distinguish itself from nearby siblings such as invite_user or add_project.

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?

There is no guidance on when to use this tool versus alternatives such as invite_user, add_member, or update_workspace_member, nor any stated prerequisites (e.g., the member must already exist in the workspace). The one-line description leaves all routing decisions to inference.

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