create_user

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

With no annotations, the description carries the full burden of disclosing behavior. It fails to mention side effects, required input structure, permissions, idempotency, or any behavior beyond the word 'mutation'. The example variables are for pagination-style queries, which could actually mislead about the mutation's purpose.

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 unstructured run-on sentence with a long variable list and an incomplete example. It is not front-loaded with a clear purpose, and the truncated example detracts from its usefulness. It could be far more concise while conveying the essential information.

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 14 parameters, one required, no annotations, and no output schema, the description is severely incomplete. It gives no indication of what the mutation returns, what errors can occur, what the 'input' object should contain, or how the many connection-style variables are used. The description is inadequate for an agent to safely invoke this tool.

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?

While schema coverage is 100%, the schema descriptions are minimal (e.g., just 'GraphQL: CreateUserInput!'). The description simply lists variable names and a cut-off example, without explaining the meaning of the required 'input' parameter or how filter/order parameters relate to a create operation. It adds no useful semantic information over 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?

The description reads 'User · mutation createUser', which is essentially a restatement of the tool name 'create_user'. It identifies the verb and resource but provides no explanation of what creating a user entails or how it differs from sibling tools like update_user or disable_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?

No guidance is provided about when to use this tool versus alternatives. The description only lists variable names and a truncated example, with no mention of prerequisites, use cases, exclusions, or relationship to other user-related tools.

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