Deletes an InfluxDB token by name to revoke access. Use for token cleanup in Core or Enterprise.
Delete an InfluxDB token by name (Core/Enterprise only).
| Name | Required | Description | Default |
|---|---|---|---|
| token_name | Yes | Name of the token to delete (required) |
Changes observed during successful MCP inspections.
v1.4.1-test.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose side effects. It indicates the action (delete) but does not mention irreversibility, permission requirements, or consequences, leaving important behavioral context out.
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?
One short sentence that is front-loaded with the action and scope, with no unnecessary words.
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 no output schema and no annotations, the description is too sparse to be fully complete; it omits return behavior, error conditions, and token type clarity, and offers no guidance on successful deletion outcomes.
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 input schema fully documents token_name with description (100% coverage). The description adds no new information beyond echoing 'by name', so it meets the baseline without adding 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 tool deletes an InfluxDB token by name and specifies it is Core/Enterprise only, distinguishing it from cloud token deletion sibling tools.
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 scoping constraint (Core/Enterprise only) implying it is not for Cloud, but it does not name alternative tools or specify when to use this versus other token deletion options.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.