delete_user

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

No annotations provided, so the description carries the full burden of behavioral disclosure. '删除用户' (delete user) states only the action and resource; it says nothing about whether deletion is permanent, what happens to associated resources (queues, bindings, permissions), or whether special permissions are required. This is severely inadequate for a destructive operation.

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 short—just two words. While it avoids verbosity, it is under-specified rather than concise; the brevity reflects missing information rather than efficient communication.

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 tool with no annotations, no output schema, and only one parameter, the description is completely inadequate. It fails to mention irreversibility, error handling, or any behavioral context that an agent needs before invoking a delete operation.

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 single parameter 'name' is fully documented in the schema. The description adds no parameter detail, but baseline 3 is appropriate when schema coverage is high.

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?

States a specific verb ('删除' = delete) and resource ('用户' = user). The sibling set includes create_user, list_users, but the description doesn't differentiate against them beyond the obvious action; still, 'delete user' is unambiguous among siblings.

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 when-to-use guidance, no prerequisites, no alternatives mentioned. An agent must infer from the name alone that deletion is irreversible and appropriate for removing a user, but nothing in the description provides that context.

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