list_groups

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

No annotations are provided, so the description carries the full burden. It does disclose what comes back (scope, type, membership counts, hierarchy), but says nothing about permissions required, result-size limits, pagination, or whether membership counts are computed at extra cost — notable gaps for an LDAP query tool.

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 opening sentence is front-loaded and the examples earn their space. The closing line 'Shows group hierarchy and management information' is vague filler that restates the earlier membership/scope claim, and the hard line wrapping adds noise without structure.

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 no output schema and no annotations, the description partially compensates by sketching the returned fields. It still leaves the agent guessing on paging/limits, the purpose of 'attributes', and how this differs from the group-member and privileged-group tools.

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%, so the baseline is 3. The examples do add real value by showing that filter_criteria takes raw LDAP syntax like '(groupType=-2147483646)' and that ou takes a full DN, but the 'attributes' parameter is never mentioned or illustrated.

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 and resource ('List groups in Active Directory') and adds scope detail — security vs. distribution groups, with scope/type/membership counts. The plural 'list' contrasts implicitly with the singular get_group and with get_group_members, but 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?

Three concrete call examples imply the usage patterns (no args, scoped to an OU, LDAP-filtered), which is more than generic guidance. However, nothing states when to prefer get_group, get_group_members, or get_privileged_groups instead, and there are no exclusions or prerequisites.

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