delete-experiment

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

The term 'soft-delete' hints at reversibility, but the description does not explain what soft-delete entails (e.g., data still exists, can be restored) or any side effects, permissions, or behavior on failure. With no annotations, more detail is needed.

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 a single sentence with no wasted words. It is front-loaded with the key action and resource.

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 the simplicity of a single-parameter delete operation, the description lacks context about prerequisites (e.g., experiment must exist), the outcome (e.g., no return value), and the reversible nature. It does not mention the sibling restore-experiment 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 coverage is 100%, and the description adds no additional meaning beyond 'by ID' and the schema's own description. The baseline of 3 is appropriate as the schema already handles parameter documentation.

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 verb (soft-delete) and resource (experiment by ID). It distinguishes from other delete tools which target different resources (e.g., delete-experiment-tag), but does not explicitly contrast with them.

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 no guidance on when to use this tool vs alternatives like restore-experiment or delete-experiment-tag. It only mentions 'by ID', which is implicit from the parameter.

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