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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered structurally. The description adds the genuinely useful fact that a confirmation token is required, but stays silent on irreversibility, cascade effects (proxy config, keys, connections tied to the API), and whether an organizationId lets an admin delete others' APIs.

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 short sentences, front-loaded with the action and followed by the hard prerequisite. No filler, though the second sentence is telegraphic to the point of omitting necessary detail.

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?

This is an irreversible destructive mutation with no output schema and no annotations covering permissions or side effects. The description does not say deletion is permanent, what else gets removed, or who may invoke it — an agent could easily call it with the wrong expectations.

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% and the schema already explains that confirmToken comes from the CONFIRMATION_REQUIRED reply and organizationId is an approved workspace id. The description names confirmToken but adds no meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb ("Deletes") and resource ("a published API"), which is more than a tautology. However, it never uses the term "user API" that the tool name and the create_user_api/update_user_api/list_user_apis siblings establish, so an agent must infer whether this touches API keys, hosted functions, or the product-level API. No sibling differentiation is offered.

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?

"Needs a confirmToken" hints at a two-step confirmation flow but the description never states when to call this versus update_user_api, delete_hosted_function, or revoke_api_key, nor what prerequisites (ownership, org admin) apply. Usage is implied only by the verb.

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