group_member_add

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

With no annotations, the description solely states the action but does not disclose traits like idempotency, side effects, or whether the user/group must pre-exist. The output schema exists but is not described.

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 extremely concise (6 words) and front-loaded with the core purpose. However, it could benefit from a bit more structure or a note about side effects.

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?

Given the presence of two required parameters and an output schema, the description is too minimal. It fails to explain context like whether the operation is additive only or what happens on duplicates.

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 0%, and the description provides no explanation for the parameters (group_id, user_id), leaving their meaning entirely to the schema's empty strings.

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 'Add a user to a group' clearly states the action and resource, and the sibling tools (group_member_remove, group_members) provide obvious differentiation.

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?

No guidance is provided on when to use this tool versus alternatives, such as group_create or acl tools. Prerequisites (e.g., group and user existence) are not mentioned.

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