mcp-activedirectory

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions recursive expansion for on-prem AD only, which is useful context, but doesn't cover important aspects like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or what the output format looks like (e.g., pagination, data structure).

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 appropriately sized with two concise sentences that front-load the core purpose and include a key behavioral detail (recursive expansion for on-prem AD). Every word earns its place with zero waste or redundancy.

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 moderate complexity (4 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and a key behavioral constraint (on-prem AD limitation for recursion), but lacks details on output format, error handling, and broader usage context that would help an agent invoke it correctly.

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%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'recursive expansion of nested groups for on-prem AD,' which aligns with the schema's description of the recursive parameter. No additional parameter semantics are provided.

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 the tool's purpose with specific verbs ('List all members') and resources ('group with user details'), and distinguishes it from siblings by focusing on group membership retrieval rather than listing groups themselves (like list_groups) or user-specific operations (like get_user_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 implies usage for retrieving group members with optional recursive expansion for on-prem AD, but doesn't explicitly state when to use this tool versus alternatives like get_user_groups (which gets groups for a user) or list_users (which lists all users). No explicit exclusions or prerequisites are mentioned.

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