passgage_create_user

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It gives no information about side effects (e.g., creating a user may trigger emails, audits, or permissions), required authentication, potential errors, or reversibility. The simple statement 'Create a new user' is entirely opaque.

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 extremely brief, but this is under-specification rather than appropriate conciseness. It consists of a single sentence that merely restates the tool's name without adding any informative content. There is no detail about input, output, or constraints, making it an inadequate description despite its brevity.

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?

The tool has one parameters object with arbitrary properties, no output schema, and no annotations, so the description must provide sufficient context for correct use. The description 'Create a new user' is grossly insufficient; it fails to explain required data fields, validation rules, response format, or any operational context needed for an agent to invoke the tool correctly.

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 input schema describes the single 'data' parameter as 'The data for creating the user' with additionalProperties allowed, giving 100% schema description coverage. However, the tool description adds no meaning beyond the schema, leaving the actual required fields and structure of 'data' completely unspecified. The baseline of 3 applies because the schema covers the parameter, but the description offers no additional semantic help.

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 'Create a new user' is a direct restatement of the tool name 'passgage_create_user', adding no additional detail or context. It does not specify any scoping, special behavior, or distinguish this tool from the many other create_* sibling tools.

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 provides no guidance on when to use this tool versus alternatives such as passgage_update_user or passgage_list_users. There are no prerequisites, no notes on authentication, and no mention of how this relates to other user management operations.

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