mcp-activedirectory

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

No annotations are provided, so the description carries full burden. It mentions 'OS and compliance status' as return data, which adds some behavioral context beyond the input schema. However, it lacks critical details like pagination behavior (implied by 'max_results' but not described), error conditions, authentication requirements, rate limits, or whether the operation is read-only/safe. For a tool with 5 parameters and no annotations, 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. Every word earns its place: 'List' (action), 'devices' (resource), 'registered or joined in Azure AD / Entra ID' (scope), and 'with OS and compliance status' (key return attributes). No wasted words 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 5 parameters with full schema coverage but no annotations or output schema, the description is minimally adequate. It specifies the resource and key return attributes, but lacks details on behavioral traits, error handling, or output structure. For a list operation with filtering, more context on result format or usage would improve completeness, but it's not entirely inadequate.

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 fully documents all 5 parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain filter syntax or compliance status details). With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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 action ('List') and resource ('devices registered or joined in Azure AD / Entra ID'), and specifies the key attributes returned ('OS and compliance status'). It distinguishes from siblings like 'get_device' by indicating it returns multiple devices with filtering capabilities. However, it doesn't explicitly contrast with 'list_computers' or 'search_computers', which might overlap in scope.

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?

No explicit guidance on when to use this tool versus alternatives like 'list_computers', 'get_device', or 'search_computers' is provided. The description implies it's for listing devices with OS/compliance info, but doesn't specify scenarios, prerequisites, or exclusions. This leaves the agent to infer usage from context alone.

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