mlflow_runs_delete

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

The description only restates the action, adding no new behavioral traits beyond what the annotations already provide (destructiveHint: true). It does not mention permanence, associated data deletion, or side effects, which would be helpful given the destructive nature.

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 extremely concise, with no wasted words. It is front-loaded with the core action. However, it could be slightly improved by adding a brief note about the destructive effect without sacrificing conciseness.

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 simple nature of the tool (1 param, destructive annotation), the description is insufficiently complete. It lacks any mention of permanence, required permissions, or what happens to the run's artifacts. The existence of an output schema does not compensate for missing behavioral context.

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?

The single parameter (run_id) is fully described in the schema with 100% coverage, and the description adds no additional context. Baseline score 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 primary action 'Delete a run', which is a specific verb on a resource. However, it does not differentiate this tool from other mlflow_runs operations like mlflow_runs_delete_tag or mlflow_runs_update, missing an opportunity to improve clarity.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, such as run existence or required permissions, leaving the agent to infer usage.

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