vibemk_delete_user

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

The description explicitly states the destructive effect: 'Remove CheckMK user'. Since no annotations are provided, this clarity is valuable, though it does not mention irreversibility or permission 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 extremely concise, with no superfluous information. It uses a clear structure: action + resource, making it easy 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?

For a simple delete operation with a single parameter, the description provides sufficient context. It does not mention edge cases like non-existent users or activation steps, but these are not strictly necessary for this tool's basic use.

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 parameter 'username' is already self-explanatory in the schema ('Username to delete'), and the description adds no additional semantic context or format details. It meets the baseline but provides no extra value.

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 specific action ('Delete user') and the resource ('CheckMK user'), making it unambiguous and distinct from sibling tools like create_user or update_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 implies usage for removing a user but does not explicitly state when to use this tool versus alternatives (e.g., using update_user to disable a user). It also lacks any prerequisites or consequences, though this is less critical given the simple scope.

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