aiworkhub_dashboard_storage_retention_preview

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

Annotations already declare readOnlyHint=true, and the description reinforces it by stating it scans without moving or deleting files, plus it discloses the side-effect-free preview_digest artifact expected by downstream tools. Return shape is covered by the output schema, so this is close to complete.

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?

Two sentences, each earning its place: the first states scope and read-only nature, the second routes to correct downstream and alternative tools. Front-loaded with the key scoping constraint.

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?

With annotations carrying the safety profile and an output schema covering return values, the description supplies the remaining needed context: what is scanned, that it is non-destructive, and how to sequence it before the mutation tools.

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?

Only one parameter with 100% schema description coverage, so the schema already fully documents include_items and the description adds nothing about it. Baseline 3 is appropriate.

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?

States a specific verb (preview) plus three concrete resources (worker worktrees, stale Git registrations, storage quarantine batches), and the READ-ONLY framing plus scoping distinguishes it clearly from sibling mutation tools like storage_quarantine and storage_registration_prune.

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?

Explicitly says to call this first to obtain a fresh preview_digest before the two downstream mutation tools, and names the alternative previews (terminal_log_retention_preview, task_retention_preview) for other resource types. Both when-to-use and when-not-to-use are covered.

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