Preview or delete completed crawl runs that fall outside the retention window, preserving only the latest runs and keeping data within the configured age limit.
Preview or delete completed runs outside a bounded retention window.
| Name | Required | Description | Default |
|---|---|---|---|
| dry_run | No | ||
| keep_latest | No | ||
| older_than_days | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose side effects. It mentions 'delete' but fails to state that deletion is permanent, that dry_run defaults to true, or that setting dry_run to false actually removes matching runs. The destructive behavior is alluded to but left ambiguous.
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?
A single tight sentence that front-loads the action and the target condition. Every word earns its place, with no wasted phrasing.
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 tool with three parameters, no annotations, and a destructive mode, the description is too sparse. It leaves the meanings of keep_latest, older_than_days, and dry_run implicit, and does not explain the preview-versus-deletion safety workflow. The presence of an output schema helps, but the missing parameter semantics remain a significant gap.
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 0%, and the description does not explain any of the three parameters. The phrase 'bounded retention window' hints at older_than_days and keep_latest but does not map them to parameters, and dry_run is completely absent. The description does not compensate for the undocumented schema.
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 action (preview or delete) applied to a specific resource (completed runs) with a qualifying condition (outside a bounded retention window). This clearly distinguishes it from siblings like delete_run or preview in scope, though it does not explicitly name 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 instead of delete_run or preview, nor does it explain the preview-then-delete workflow via dry_run. The retention-current use case is implied but not explicitly stated as the preferred cleanup path.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.