User Groups

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

readOnlyHint=true already establishes this is a safe read, lowering the bar. The description adds that traversal is nested/recursive by default, which clarifies result scope, but it restates the schema default and says nothing about truncation under limit or what 'domain' changes.

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?

A single front-loaded sentence with no filler, and the recursive-by-default caveat is attached directly to the verb. Brevity is appropriate; the shortfall is coverage, not verbosity.

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?

With an output schema present, return values need no explanation, but four parameters at 0% schema coverage and only a readOnlyHint annotation leave real gaps. An agent cannot tell whether 'user' takes a DN or sAMAccountName, what domain scoping does, or whether limit silently truncates recursive results.

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 0% for 4 parameters. The description only touches 'user' and the nested default; 'limit' (default 1000) and 'domain' (nullable, default null) are wholly unexplained in both schema and description, leaving an agent guessing how to scope a multi-domain lookup.

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?

States a specific verb+resource: list the groups a given user belongs to. The direction (user → groups) is clear enough to distinguish it from the reverse sibling group_members, though no sibling is named explicitly.

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?

Usage is only implied by the description; there is no explicit guidance on when to prefer this over group_members or is_member, and no mention of prerequisites such as needing a DN vs. a username for the required 'user' parameter.

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