create_user

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

The description only says 'create' with no disclosure about side effects, duplicate email handling, authentication requirements, or rate limits. With no annotations, the agent lacks critical behavioral context.

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 sentence, which is concise, but it sacrifices clarity and completeness. It is front-loaded but lacks structured details that would help the agent understand the parameters or usage.

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 the nested input schema, required fields, and lack of annotations or output schema, the description is insufficient. It does not cover optional fields like password or group_ids, nor does it explain the return value.

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?

The description adds no meaning beyond the input schema. The 'input' object is not described, and the schema's property descriptions are not referenced. The 0% schema coverage at the top level is not compensated.

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 (create) and resource (user) and context (Metabase), distinguishing it from sibling tools like create_action or create_api_key. However, it lacks specificity about the required fields and optional parameters, which would make it clearer.

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 other user-related tools (e.g., update_user, delete_user) or any prerequisites. The agent has no context on scenarios like SSO setup or permission group assignment.

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