ml_experiment_delete

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a destructive operation. The description confirms the target resource but adds no further behavioral context such as irreversibility, cascading deletion of experiment data, or authorization requirements.

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, front-loaded sentence with no filler, repetition, or unnecessary detail. It is appropriately sized for a simple two-parameter delete operation.

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 fully documented two-parameter schema and destructive annotations, the description is minimally sufficient for an agent to select and invoke the tool. It is incomplete only in that it does not mention whether deletion is permanent, what side effects may occur, or what a successful result looks like, and there is no output schema to clarify this.

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%, and both required parameters have clear descriptions ('The workspace ID' and 'The ML experiment ID'). The tool description does not add parameter-level meaning, but the schema already provides adequate information.

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 states a specific verb ('Delete') and a clear resource ('an ML experiment'), making the operation unambiguous. It is readily distinguishable from sibling tools such as ml_experiment_create, ml_experiment_update, ml_experiment_get, and ml_experiment_list.

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?

There is no guidance on when deletion is appropriate, how to obtain the workspaceId or mlExperimentId, or what to do instead of deleting. The description only names the operation, leaving usage context to be inferred from the tool name and sibling list.

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