aiworkhub_dashboard_terminal_log_retention_preview

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful scope: it 'scans process logs read-only while excluding the canonical request ledger' and returns a 'preview_digest' for the subsequent quarantine step. It does not describe pagination behavior or return format, but with annotations and an output schema, that is a minor gap.

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, front-loaded with 'READ-ONLY' and the core purpose, then routing guidance. No filler; every clause contributes to correct selection.

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?

Given the output schema exists and the schema fully documents parameters, the description covers everything an agent needs: purpose, safety, scope (excludes request ledger), and precise routing to alternatives. Nothing material is missing.

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 both parameters (limit, cursor) are fully documented with defaults, clamping, and semantics. The description adds no parameter-specific detail beyond what the schema provides, so the baseline of 3 applies.

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) and resource (reclaimable terminal process log files, protected logs, terminal-log quarantine batches) and distinguishes itself from siblings by naming the quarantine and usage_backfill tools. An agent can tell exactly what this tool enumerates without opening the schema.

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 when to call this tool ('before aiworkhub_dashboard_terminal_log_quarantine'), what it produces ('preview_digest'), and names two alternatives with their conditions ('usage_backfill when runs lack usage receipts', 'storage_retention_preview for worktrees'). This is near-complete routing guidance.

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