create_user

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that an activation email is sent and that a preview mode exists without confirm=true. It still omits permission requirements, error behavior for duplicate emails, reversibility, and what happens to other defaulted fields.

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 two short sentences, front-loading the core action and its side effect. The roles and confirm notes are efficient and there is no wasted text.

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 7-parameter creation tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It omits required-field guidance beyond relying on the schema, does not clarify name versus first_name, and says nothing about the returned user object or error handling.

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 0%, so the description must compensate for all 7 parameters. It explains only roles (list of role IDs, see get_roles) and confirm (preview behavior); the remaining five parameters, including the confusing name vs first_name distinction, phone_number, and preferred_language, are undocumented.

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 states a specific verb and resource: 'Crée un membre' (creates a member). It also adds the key side effect that an activation email is sent. It does not explicitly distinguish itself from sibling tools like update_user or add_signup, but the creation action is clear.

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?

It gives one important usage condition: 'Sans confirm=true : aperçu seulement' (without confirm=true, preview only). This tells the agent how to avoid unintended creation. However, it does not state when to use this tool versus alternatives such as update_user or add_signup, nor does it mention prerequisites like permissions.

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