Create Admin Users Unlock

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

With no annotations, the description must disclose behavioral traits, but 'Unlock Users' provides none. It does not mention side effects, reversibility, permission requirements, whether the action applies to one user or many, or what the 'force' parameter does.

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 short but under-specified rather than concise. The two-word phrase provides no structured or front-loaded information that helps an agent understand the operation.

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?

For an admin mutation tool with no annotations and 0% schema description coverage, 'Unlock Users' is severely incomplete. The agent is left without the scope, target, parameters, or consequences needed to safely select and invoke the 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?

Schema description coverage is 0%, and the description does not mention either parameter. An agent cannot know what 'force' means or how to provide 'accept-language' beyond their raw names and types.

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 'Unlock Users' is essentially a restatement of the tool name and title. It identifies a verb and a resource but adds no information about what 'unlock' means, whether it applies to admin user accounts, or how it differs from sibling admin user 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?

No guidance is given for when to use this tool versus alternatives such as create_admin_users, update_admin_users_by_item, or create_admin_users_password_reset_token. The context of 'locked users' is implied but never stated, and no prerequisites or exclusions are mentioned.

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