Aedifion MCP Server

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

No annotations provided, so description carries full burden. 'Initial password' hints at temporary credentials but misses critical behavioral details: permissions required, idempotency/duplicate handling, whether welcome emails are sent, or what the output schema contains.

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?

Front-loaded purpose statement followed by structured Args block. No redundancy or waste. Slightly unusual formatting but clear and 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?

User creation is a high-permission operation with complex error conditions (duplicates, validation), yet the description lacks behavioral context. Output schema exists (reducing description burden for return values), but mutation semantics and company/realm distinctions remain under-documented.

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 documenting all 4 parameters in the Args block. Descriptions are minimal (e.g., 'First name' for first_name) but provide basic type semantics missing from the schema.

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?

States specific verb (Create) + resource (user) + scope (in the company). Distinguishes from realm-level siblings like get_realm_users via 'company' qualifier, but does not differentiate from update_user for existing 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 explicit guidance on when to use this versus update_user for existing users, or prerequisites like admin permissions. No alternatives or exclusions mentioned.

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