yougile_delete_user

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

Annotations already communicate destructiveHint=true and readOnlyHint=false. The description adds minimal context by specifying the removal is from the 'company', but does not disclose whether this is permanent, what happens to the user's data, or any authorization requirements.

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 one concise sentence without fluff. It front-loads the action and is appropriately small for a simple delete operation.

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 the simple one-parameter schema and destructive annotation, the description is minimally sufficient but lacks context on side effects (e.g., whether removal is permanent, impact on projects/tasks). There is no output schema, so return values are not documented.

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 fully documents the single 'id' parameter as a User UUID (100% coverage). The description adds no additional parameter semantics, such as how to obtain the id or format expectations.

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 clearly states the action ('Remove a user') and the scope ('from the company'). This distinguishes it from sibling tools like update_user, invite_user, and list_users.

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 vs alternatives. The description does not mention prerequisites, consequences, or alternate approaches such as deactivating vs deleting. It relies solely on the tool name and destructive annotation.

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