vibo_remove_user

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

Description adds the 'Confirm-gated' behavior beyond annotations, indicating a two-step process with preview. However, it does not disclose what the preview returns or whether the action is reversible. Annotations indicate readOnlyHint=false, so the write nature is expected, but more context (e.g., permission requirements) would improve transparency.

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?

Two sentences capture the essence without redundancy. Every word is necessary, and the structure is front-loaded with the core action.

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?

With 3 parameters and no output schema, the description is minimal but sufficient for a straightforward removal action. However, it lacks context on post-removal effects (e.g., notifications, cascading changes) and fails to guide the agent on when a preview occurs versus actual removal.

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% with descriptions for each parameter. The description adds no further semantic value beyond the schema; 'Confirm-gated' reinforces the confirm parameter's role but is already evident from the schema description 'Must be true to proceed'.

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 'Remove a member from an event' with a specific verb ('Remove') and resource ('member from an event'). It distinguishes from siblings like vibo_leave_event (self-leave) and vibo_invite_users (invite) by implying this action is performed by an organizer on another 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?

Only mentions 'Confirm-gated' but does not explain when to use this tool vs alternatives (e.g., vibo_leave_event for self-removal, or vibo_change_user_role for modifying roles). No explicit when-not or prerequisites are provided.

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