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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is partly covered. The description still adds genuine value by disclosing the side effect that content keeps its labels (i.e., labels are not deleted with the experiment) and by mandating user confirmation. The duplicated 'DESTRUCTIVE' warning is redundant with the annotation but does not contradict it.

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 destructive warning and the confirmation requirement, with zero filler. The bracketed '[DESTRUCTIVE]' duplicates the inline 'DESTRUCTIVE', which is a small redundancy.

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?

For a single-parameter delete with no output schema, the description covers what is deleted, what is preserved, that confirmation is required, and the underlying API call. The only real gap is the semantics of the 'id' argument, which neither the schema nor the description clarifies.

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?

There is one parameter with 0% schema description coverage, so the schema contributes nothing. The description does not explain the 'id' parameter directly, though the embedded endpoint hint (DELETE /api/v2/experiments/{id}) implies it is the experiment identifier. That is minimal compensation for the coverage gap.

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+resource ('deletes the experiment record') and distinguishes the operation from its siblings by clarifying scope: only the experiment record goes, content keeps its labels. An agent can tell it apart from delete_content, delete_queue, and update_experiment without opening any 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?

'Ask the user before calling' gives a clear confirmation prerequisite, which is meaningful guidance for a destructive action. However, it names no alternatives (e.g., update_experiment, get_experiment) and gives no when-not condition, so the routing guidance is only implied.

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