aad_create_user

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

Description only states 'create' without detailing side effects (e.g., duplicate handling, password expiry, default settings). No annotations provided; tool carries mutation risk with minimal disclosure.

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?

Clear, front-loaded purpose sentence followed by a parameter list. No wasted words, but could be slightly more concise by grouping optional parameters.

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?

Covers all parameters and required fields. Output schema exists but is not referenced. Lacks context on error handling, idempotency, or post-creation behavior.

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 compensates by listing all parameters with brief semantic hints (e.g., 'Display name for the user'). However, missing constraints like format or length.

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?

Description explicitly states 'Create a new Azure AD user,' with clear verb and resource. It distinguishes from sibling tools like aad_delete_user and aad_list_users.

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 guidance on when to use this tool versus alternatives, no prerequisites or context about required permissions (e.g., admin consent). Only parameter roles are implied.

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