aad_list_users

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 not disclose that the tool returns a capped list (default top=50), pagination behavior, required permissions, or any side effects. This lack of detail leaves behavioral expectations unclear.

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 concise and front-loaded with the purpose. The argument block uses a structured format. However, it could be slightly more organized (e.g., separating purpose from args more clearly) but overall efficient.

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?

For a simple list tool with two parameters and an output schema, the description provides the essential purpose and parameter details. It lacks mention of return format (list of users) and pagination behavior, but the output schema likely covers return structure. It is adequate but not fully complete.

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?

With 0% schema description coverage, the description adds meaningful context: it explains the 'filter' parameter as an OData query with an example, and 'top' as a maximum count with default. This goes beyond the schema's basic type information.

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 'List Azure AD users', which is a specific verb-resource pair. It distinguishes from siblings like aad_show_user, aad_create_user, etc. However, it could be more explicit about the scope (e.g., listing all users with optional filtering).

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 aad_show_user or aad_list_applications. The description does not mention when not to use it or provide context for selection among similar list tools.

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