tc_add_group_users

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

The description adds meaningful behavioral context beyond the annotations by stating the TC_ENABLE_WRITE=1 requirement and the precondition that users must already be project members. It also describes the return shape, which is not in annotations. No contradictions with annotations.

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 well-structured and front-loaded with the core purpose. It uses concise sections for requirements, prerequisites, arguments, and return value, with no wasted words. Every sentence adds value.

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 tool's simplicity (3 params, no enums/nested objects) and the presence of an output schema, the description is complete. It includes preconditions, environment requirements, parameter semantics, and return format, covering all essential usage aspects.

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 schema description coverage at 0%, the description compensates by explaining each parameter. It clearly identifies project_id and group_id as IDs, and user_ids as 'Member ids from tc_list_project_members', which provides valuable source context beyond the schema's bare property titles.

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 states 'Add project members to a group' with a specific verb and resource. This clearly differentiates it from sibling tools like tc_add_project_user (adds users to a project) and tc_remove_group_users (removes users from a 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 clear usage context: it requires TC_ENABLE_WRITE=1 and specifies that users must already be project members, referencing tc_add_project_user for the prerequisite. It does not explicitly list alternative tools for removal, but the context is strong.

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