ghl_delete_user

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Remove a team member' without stating that this is a permanent deletion, that it may have irreversible consequences, or that specific permissions are required. For a destructive operation, this lack of disclosure is a significant gap.

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 a single, concise sentence that is front-loaded with the action and resource. It contains no filler or redundant information, making it easy for an agent to parse quickly.

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?

This is a one-parameter destructive tool with no output schema and no annotations. The description is minimal and does not elaborate on the outcome, error handling, or whether the deletion is permanent. For a deletion operation, this level of completeness is insufficient for an agent to understand the full impact.

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 input schema has 100% coverage for the single parameter 'userId', with its description 'User ID to delete' being self-explanatory. The tool description adds no extra meaning beyond the schema, which is acceptable given the high schema coverage, but it does not compensate for any potential ambiguity in parameter format or source.

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 ('Remove') and the resource ('a team member') with the context 'from the location'. This specific wording distinguishes it from sibling user tools like ghl_create_user or ghl_update_user, leaving no ambiguity about what the tool does.

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 no guidance on when to use this tool versus alternatives, such as ghl_update_user for updating roles or ghl_get_user for viewing. It also does not mention any prerequisites, side effects, or alternatives for revoking access versus deleting a user.

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