lattice_delete_user

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

The description only labels the operation as 'Destructive', which is minimal. With no annotations, the agent needs more disclosure: e.g., whether the deletion is permanent, cascading effects on related data, required permissions, or any safety warnings. This is insufficient for a delete 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 brief (two words plus 'Destructive'), which is concise but sacrifices completeness. It is front-loaded with the action, but the terse nature means it fails to provide necessary context. It earns its place but needs expansion.

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 it is a destructive deletion tool with no output schema and no annotations, the description should include information about return values, error handling, or confirmation. The current description is too sparse for an agent to fully understand the tool's behavior.

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 coverage is 100% for the single parameter 'id', which is described as 'User ID' in the schema. The description adds no extra semantics beyond what the schema provides. Baseline score of 3 is appropriate.

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 ('Delete') and resource ('Lattice user'), which is specific. However, it does not distinguish this tool from siblings beyond the action itself; more context on scope (e.g., 'Permanently removes a user from the system') would improve differentiation.

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 on when to use this tool versus alternatives like lattice_update_user or lattice_list_users. The description lacks any context about prerequisites, conditions, or when not to use it.

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