Benutzer löschen

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

Since no annotations are provided, the description carries full burden for disclosing behavioral traits. It does not state that the deletion is permanent, that content will be reassigned, or mention any side effects or error conditions. The mention of 'reassign' hints at content transfer but does not elaborate on the destructive nature.

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?

A single, front-loaded sentence conveys the action and a critical prerequisite without any extraneous words. It is efficient and immediately informative.

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 a destructive mutation tool with no annotations and no output schema, the description is too minimal. It omits important context such as permanence, effects on user content, expected response, and error scenarios, leaving the agent without sufficient information to understand the full impact of invoking 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?

Schema description coverage is 100%, so the baseline is 3. The description's mention of reassign simply repeats a required parameter without adding new meaning. It does not clarify the roles of userId or force beyond the schema's existing descriptions.

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 clearly states the action ('Löscht' = deletes), the resource ('WordPress-Benutzer'), and a key requirement ('erfordert Reassign'). It unambiguously distinguishes this from sibling admin tools like admin_create_user or admin_update_user by indicating deletion.

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 includes a usage prerequisite: reassign is required. This provides clear context for when the tool is appropriate. It does not explicitly mention alternatives or exclusions, but the tool name and purpose make the primary use case evident.

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