delete_user

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

No annotations are supplied, so the description carries the full behavioral burden. It does not state whether deletion is permanent, whether it requires elevated permissions, whether associated data (tests, findings, notes) is cascaded, or whether it is reversible. 'Delete' implies destruction but no consequence detail is given.

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?

Very short and front-loaded, which is good, but the 'Args:' block largely duplicates the schema and the overall text is under-specified rather than efficiently informative. Adequate structurally with no waste to cut, but no substance added.

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?

An output schema exists, so return values need not be described. However, for a destructive tool with zero annotations and no permission/cascade/reversibility context, the description is thinner than the operation warrants. It is minimally complete but leaves significant behavioral gaps.

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%, so the description must compensate. It restates the single required parameter ('user_id: The user ID to delete') but adds no meaning beyond the property name and type already in the schema. Marginal value only.

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 and resource ('Delete a user'), which is clear on its own. However, it offers no differentiation from siblings like delete_organization, delete_product, or delete_engagement, and nothing distinguishes it from update_user semantics beyond the verb. Minimum viable clarity.

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, when-not-to-use, or alternative guidance is provided. For a destructive, irreversible operation there is ample opportunity to explain context (e.g., use update_user to deactivate instead, or confirm authorization) and none is taken.

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