Remove a user from an organization

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

No annotations are provided, so the description must carry the full behavioral disclosure. It does disclose irreversibility, which is a key trait. However, it omits other behavioral aspects like required permissions, whether related data is cascade-deleted, or what happens on failure. The single caution adds some value but is not comprehensive.

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, front-loaded sentence plus a clear caution. Every word earns its place; there is no redundancy or fluff.

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 a simple two-parameter tool with no output schema and no annotations, the description provides the essential action and irreversibility. However, it lacks details about return values, error behavior, or prerequisites, leaving some ambiguity for a high-stakes irreversible operation.

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 only mentions 'by id', which loosely corresponds to userId but does not clarify the optional 'organization' parameter. The schema's property names are self-explanatory but the description adds minimal meaning beyond them.

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 (revoke)'), the target ('a user from an organization'), and the method ('by id'). This distinguishes it from sibling tools like wflow_delete_role or wflow_upsert_user.

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?

There is no explicit guidance on when to use this tool versus alternatives. The 'Irreversible' warning is a caution, not a usage guideline. Unlike tools that name alternatives or prerequisites, this description provides no such context.

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