mdrun_cleanup

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

While annotations already indicate destructive behavior (destructiveHint=true), the description adds minimal context beyond stating 'remove'. It does not detail what happens to the removed records (e.g., permanent deletion), whether the operation is reversible, or any side effects. For a destructive tool, more transparency 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 concise sentence that efficiently conveys the core action. No redundant or extraneous information is present.

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?

Despite the tool's simplicity (one optional parameter, output schema exists but not detailed), the description is incomplete. It fails to mention the parameter's effect or the nature of the output. An agent would lack sufficient context to use the tool correctly without inferring from the parameter name.

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?

With 0% schema description coverage, the description should compensate by explaining the 'finished_only' parameter. However, the description ignores parameters entirely, providing no meaning beyond the schema's title and default value. The agent must rely solely on the schema, which is insufficient.

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 uses a specific verb ('Remove') and resource ('finished job records from the registry'), clearly distinguishing it from sibling tools like mdrun_start, mdrun_list, etc. It leaves no ambiguity about what the tool does.

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 such as mdrun_forget or mdrun_stop. The description does not mention contexts, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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