cleanup_preview

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

With no annotations provided, the description carries the full behavioral transparency burden. It explicitly discloses the non-destructive nature ('without deleting anything') and outlines the selection criteria ('unimportant, never accessed, old'). This goes beyond simply stating the tool's function and provides useful safety-relevant behavior.

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 front-loads the core purpose. Every word contributes meaning, with no filler or redundancy.

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 simple preview tool with one optional parameter and no output schema, the description provides a clear purpose, selection criteria, and non-destructive guarantee. The main gaps are the undocumented limit parameter and the lack of explicit output format, but the low complexity and clear intent make it reasonably complete.

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 schema contains one optional 'limit' integer parameter with 0% description coverage. The tool description does not mention this parameter or explain how it affects the preview, leaving it entirely up to the agent to infer from the parameter name. Since the description was expected to compensate for the lack of schema documentation, this is a notable omission.

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 tool's function: it previews which episodic traces would be recycled by the sleep prune pass. It distinguishes itself by explicitly noting that nothing is deleted, setting it apart from the actual sleep prune tool.

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 phrase 'without deleting anything' provides clear context for when to use this tool (as a safe dry run before the sleep prune). However, it does not explicitly name alternative tools or state when not to use it, though the contrast with the actual sleep pass is implied.

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