jumpcloud_user_token_delete

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It says 'Destructive' and 'Risk: high,' but these merely restate what a delete operation implies. It does not specify irreversibility, required permissions, cascade effects, or any details beyond the inherent destructive nature.

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 very brief and front-loaded: 'Mutating token deletion. Use when removing obsolete user tokens from Vault. Destructive. Risk: high.' No filler or unnecessary detail; however, 'Mutating' and 'Destructive' are slightly redundant, which keeps it from a perfect score.

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 destructive delete operation with four parameters, no annotations, and no output schema, the description is too sparse. It does not address parameter meanings, error behavior, or preconditions, leaving significant gaps for an agent to navigate safely.

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%, and the description does not explain any of the four parameters (userId, tokenId, tenantId, authorizationKey). The required tokenId is not described, and there is no guidance on how the parameters relate to the operation.

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 ('Mutating token deletion') and the target resource ('user tokens from Vault'), using a specific verb and resource. It distinguishes itself from sibling tools like jumpcloud_user_token_list and jumpcloud_user_token_upsert by explicitly framing it as a removal operation.

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?

Provides a clear context for when to use the tool: 'Use when removing obsolete user tokens from Vault.' While it names one specific scenario, it does not include explicit exclusions or mention alternatives such as deactivating tokens (jumpcloud_user_token_set_active), so it falls short of a full 5.

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