whodb_platform_delete_ontology_fast_lookup

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds non-annotation context: the default mode only previews and returns a confirmation token, and that workspace targeting does not mutate session defaults. It still doesn't say what collateral effects the deletion has or whether it is reversible.

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 tight sentences, purpose front-loaded, no filler. There is minor overlap with the schema's own workspace description, but nothing wasteful.

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?

No output schema exists, so the description must carry the flow, and it does enough: it explains that the default call yields a token rather than performing the delete and that workspace selection is per-call. It omits what a confirmed deletion actually removes and whether recovery is possible, which matters for a destructive tool.

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 100%, so the schema already documents both 'id' and the nested workspace object. The description restates workspace targeting ('per-call targeting without changing defaults') with no added syntax or format detail beyond what the schema provides.

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 and resource ('Delete one hosted ontology fast lookup by id'), which cleanly separates it from the sibling create/lookup tools. An agent can identify the target and the operation without opening the schema.

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?

Explains the two-step confirm workflow ('default mode returns a confirmation token; do not call whodb_platform_confirm until the user approves'), which is real procedural guidance for this specific tool. It stops short of saying when an agent should not delete or what alternatives exist (e.g. archive/restore), so it falls below a 5.

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