openai_remove_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 simply states the action without mentioning that removal is likely permanent, may require admin permissions, or could affect the user's access across all projects. This is a significant gap for a destructive 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 concise, front-loaded with the main action, and includes a single parameter explanation. Every word earns its place with no redundancy.

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?

For a simple tool with one parameter and an output schema, the description is adequate at a basic level. However, it lacks important context such as irreversibility, permission requirements, or the distinction from project-level removal. Given the presence of a sibling tool for project removal, more contextual guidance would be beneficial.

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 description defines user_id as 'The member's user ID' and references openai_list_users to obtain it. This adds minor semantic value beyond the schema's bare property name, but it does not explain the ID format or any constraints. Since schema coverage is 0%, the description partially compensates but remains minimal.

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 a member from the organization') with a specific verb and resource. This distinguishes it from sibling tools like openai_update_user_role or openai_remove_project_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?

The description provides a helpful pointer to openai_list_users for obtaining the user_id, but does not clarify when to use this tool versus alternatives like openai_remove_project_user (which removes from a project) or openai_invite_user. This omission could lead to incorrect tool selection.

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