delete_api_token

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

Annotations are absent, so the description bears full responsibility for behavioral disclosure. It only says 'Delete from the Database' without indicating side effects like whether the deletion is permanent, if it invalidates active sessions, or if any authorization is required.

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 short but includes a redundant HTTP method line that repeats information. It is not strictly concise; it could combine the title and action into one sentence.

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?

Despite the tool's simplicity, the description omits crucial context such as expected return value, error cases, permission requirements, and whether the token belongs to the current user. With no output schema or annotations, this is insufficient.

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 has no descriptions for parameters (0% coverage), and the description adds no explanation of what 'token_id' represents or how to obtain it. The parameter semantics are entirely unmet.

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 'Delete api_token from the Database,' making it obvious the tool deletes an API token. The tool name and endpoint format reinforce the purpose. While the purpose is clear, it does not distinguish from other delete operations or specify the token type.

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?

No guidance is provided on when to use this tool versus alternatives like create_api_token, get_token, or other delete tools. There is no mention of prerequisites, such as needing the token's ownership or authentication status.

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