sophos_add_users_to_group

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

No annotations provided. The description does not disclose behavioral aspects like idempotency (e.g., what happens if a user is already in the group), whether the operation is atomic, or any side effects. Users must infer behavior from the schema.

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?

Single-sentence description is efficient and front-loaded with the core action. No redundant text, though it could benefit from a brief note on usage context.

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 simple mutation with no output schema and 3 required parameters, the description is minimally adequate. However, it lacks details on expected behavior for duplicate users, error scenarios, or limits (e.g., number of users per call).

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% and each parameter has a basic description. However, the tool description adds no additional meaning (e.g., format of comma-separated user_ids, relationship between tenant_id and group_id). Baseline of 3 is appropriate.

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 'Add one or more users to a directory user group,' specifying the verb (add), object (users), and target (group). It distinguishes from siblings like sophos_remove_users_from_group and sophos_add_user_to_groups (singular vs plural), but does not explicitly differentiate its scope.

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 on when to use this tool versus alternatives such as sophos_add_user_to_groups (singular) or bulk operations. Lacks context about prerequisites, batch size limits, or error handling.

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