create_user

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 discloses the 422 error for duplicate emails, role defaults, and return value. However, it does not mention side effects, permission requirements, or rate limits. It adds moderate behavioral context beyond the schema.

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?

Two sentences, front-loaded with purpose, no filler. Every sentence adds essential information: creation, constraint, default role, return. Highly 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?

Given 7 parameters, no output schema, and no annotations, the description covers key aspects: creation, uniqueness, role options, return value. It could mention required fields (name, email) but these are in schema. Nearly complete for the tool's complexity.

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 coverage is 100% with descriptions for all 7 parameters. The description adds extra semantics: email uniqueness constraint and role default. This goes beyond the schema's enum listing, providing meaningful context for agent decision-making.

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 uses the precise verb 'Create' and resource 'Zendesk user', and includes specific details about email uniqueness, role defaults, and return value. It clearly distinguishes this tool from siblings like 'update_user' or 'delete_user'.

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?

The description mentions email must be unique and role defaults to end-user, providing context for when to use. It lacks explicit alternatives or when-not-to-use, but the creation purpose is clear. A 4 is appropriate for providing clear context without exclusions.

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