sophos_list_user_groups

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

Annotations already declare readOnlyHint=true and destructiveHint=false, signaling safe read-only operation. The description adds minimal behavioral context (scoping to a tenant's directory) but doesn't disclose pagination behavior, rate limits, or other traits beyond what annotations provide.

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 sentence of six words, making it highly concise. However, it packs minimal information and could benefit from a bit more context without losing conciseness. It earns its place but is not exceptionally structured.

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 has four parameters (all well-documented in schema), read-only annotations, and no output schema, the description is adequate but not thorough. It omits mention of pagination or common usage patterns, which would help in complex scenarios. Complete enough for a simple list operation but could be improved.

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 100%, with all four parameters described. The description does not add any meaning beyond the schema definitions, which already specify types and roles (e.g., tenant_id required, search for filtering, page_key for pagination). Baseline score of 3 applies.

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 uses a specific verb 'List' and resource 'user groups', clearly indicating the tool's purpose. It distinguishes it from sibling tools like sophos_create_user_group and sophos_update_user_group which modify groups.

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 states the basic use case (list user groups in a tenant) but does not provide guidance on when to use this tool versus alternatives like sophos_get_user_group for a single group or sophos_list_users_in_group for members. No exclusions or context are given.

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