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 filtering capabilities but fails to describe critical behaviors: whether this is a read-only operation (implied by 'List' but not explicit), pagination or rate limits, authentication requirements, or what the output format looks like (e.g., list of user objects). For a tool with 4 parameters and no annotation coverage, this is a significant gap.

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, efficient sentence that front-loads the core purpose ('List Active Directory or Azure AD users') followed by key capabilities ('with optional filters'). Every word earns its place with zero redundancy or wasted phrasing, making it easy to parse quickly.

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 complexity (4 parameters, no annotations, no output schema), the description is incomplete. It covers the basic purpose and filtering but omits essential context: output format, behavioral traits like safety or side effects, and differentiation from sibling tools. For a list operation in a directory service with multiple similar tools, more guidance is needed.

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 marginal value by mentioning filtering by 'name, email, or department' (which aligns with the 'filter' parameter) and specifying the data sources, but doesn't provide additional semantics beyond what's in the schema. This meets the baseline for high schema coverage.

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 verb ('List') and resource ('Active Directory or Azure AD users'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_user' (singular) and 'search_users' by emphasizing listing with optional filters rather than specific search or retrieval. However, it doesn't explicitly differentiate from 'list_groups' or 'list_computers' beyond the resource type.

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 provides no guidance on when to use this tool versus alternatives like 'get_user' (for single user retrieval) or 'search_users' (which might offer different filtering capabilities). It mentions optional filters but doesn't clarify scenarios where this tool is preferred over sibling tools, leaving usage context entirely implicit.

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