Create a user

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

With no meaningful annotation coverage beyond non-read-only flags, the description carries the behavioral burden well. It discloses the side-effect boundary—pre-creating only a Woodpecker record, not granting forge access—and the confirmation behavior for admin=true ('asks a person first').

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?

Three sentences with the core purpose front-loaded, followed by important scope caveats and the admin confirmation behavior. Every sentence adds useful information without filler.

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 output schema exists and all parameters are documented in the schema. The description supplies the missing contextual pieces: permission level, timing, side-effect scope, and admin confirmation, making it sufficiently complete for correct invocation.

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 100%, so the baseline is 3. The description adds no new parameter-level meaning beyond what the schema already documents; the 'asks a person first' note repeats the admin parameter's schema description.

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: 'Registers an account ahead of its first login.' It further clarifies this is not a forge-level creation and only 'pre-creates the Woodpecker record,' which clearly distinguishes it from sibling create_* tools like create_agent, create_forge, or create_secret.

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 gives clear conditions: use it before first login and it is admin-only. It also states a when-not by explaining that 'this does not create anything in the forge and grants no access there,' but it does not name any alternative sibling tool explicitly.

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