clean_sandbox_artifacts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies deletion via 'sweep' and 'recover disk space', but does not state that files are irreversibly removed, what 'verified' means, whether dry-run is the default, or what permissions are required.

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 or repetition. It is appropriately sized, though the space saved by conciseness could have been used to disclose critical deletion behavior.

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 destructive cleanup tool with no annotations and no output schema, the description is too thin. It should explain what gets deleted, how safety is ensured, and how dry-run interacts with real deletion, especially since the schema already defines these parameters but the description does not tie them together.

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%, so all three parameters are already documented with useful detail, including dryRun behavior and minAgeMinutes semantics. The description does not add meaning beyond the schema, which is the expected baseline when schema coverage is high.

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/resource combination: 'sweep verified transient files and directories' with the goal of recovering disk space. It is clear that this performs cleanup, but it does not explicitly distinguish itself from the sibling scan_sandbox_artifacts tool or state that it deletes rather than reports.

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 explicit guidance on when to use this tool versus the sibling scan_sandbox_artifacts, nor any conditions for when not to use it. The phrase 'maintain repository cleanliness' implies usage but does not give the agent actionable selection criteria.

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