delete_user

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

No annotations are provided, so the description must disclose behavioral traits. It indicates the tool is destructive ('Delete'), but fails to mention whether the action is reversible, what data is affected, required permissions, or side effects. The requirement for confirm=True adds a small degree of transparency, but overall the description is minimal.

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 very concise, using two short sentences to convey the action and the requirement. It is front-loaded with the main verb. There is no extraneous information, though it could be combined into a single clearer sentence. It earns its place by being efficient.

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?

Given that this is a destructive tool with no annotations, the description is incomplete. It does not explain the return value (though an output schema exists), error conditions, cascading effects, or permissions required. The requirement for confirm=True is noted, but many critical contextual details are missing, making it inadequate for safe use.

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 schema has 0% description coverage, so the description should compensate. It adds meaning for 'confirm' by stating it must be True, which goes beyond the schema (which only shows default false). However, it provides no additional semantics for 'user_id', leaving its meaning to the schema. The description partially compensates for the lack of schema 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?

Description states 'Delete a user' which clearly identifies the action (delete) and resource (user). It distinguishes from sibling tools like delete_dataset because the resource is different. However, it does not elaborate on scope or any special cases, but the core purpose is unambiguous.

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 some guidance by stating 'Requires confirm=True', implying that the deletion is conditional. However, it does not specify when to use this tool versus alternatives (e.g., disabling a user), nor does it indicate prerequisites or context for use. The guidance is limited to the confirm parameter.

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