add_group_member

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

With no annotations provided, the description carries full burden but offers minimal behavioral information. It doesn't disclose whether this is a mutating operation (implied by 'Add'), what permissions are required, whether there are rate limits, what happens if users are already members, or what the return value looks like. For a mutation tool with zero annotation coverage, this is inadequate.

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 - a single sentence that states the core purpose and one important constraint. There's no wasted verbiage, and the key information is front-loaded. However, it may be too brief given the tool's complexity as a mutation operation with no annotations or output schema.

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 mutation tool with no annotations, no output schema, and 2 required parameters, the description is insufficiently complete. It doesn't explain what happens after adding members, what errors might occur, what permissions are needed, or what the tool returns. The 'Qiita Team only' constraint is helpful but doesn't compensate for the missing behavioral context needed for safe invocation.

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 parameters ('url_name' and 'user_ids') clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to guidelines, when schema coverage is high (>80%), the baseline is 3 even with no param info 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 description clearly states the action ('Add members') and resource ('to a group'), with the specific constraint 'Qiita Team only' indicating it's not available for all users. It distinguishes from sibling 'remove_group_member' by specifying addition versus removal, but doesn't explicitly differentiate from other group-related tools like 'create_group' or 'update_group'.

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 provides minimal guidance - only that it's for 'Qiita Team only'. It doesn't specify when to use this tool versus alternatives like 'create_team_invitation' or 'list_group_members', nor does it mention prerequisites such as needing admin permissions or existing group membership. No explicit when-not-to-use guidance is provided.

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