prune_flatten_artifacts

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

Without annotations, the description fully carries the burden. It discloses that files are deleted, highlights dry-run default for safety, and explains consequences of include_sidecars=true (breaks retrieve_flattened/unflatten_session). Also mentions age filtering.

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 well-structured sentences with no wasted words. Front-loaded with the action and key details.

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?

The tool's behavior is fully described given its simplicity. No output schema is needed, as the tool reports deletions. All relevant parameters are explained with context.

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 has 100% coverage, but description adds extra meaning: explains why sidecars are kept by default (needed by retrieve_flattened), and that dry_run defaults to true for safety. This augments the schema descriptions.

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 it reclaims disk by deleting specific artifact types (.bak, .preunflatten.bak, stale .tmp-<pid> files) for a project. It distinguishes itself from sibling tools like flatten_session or unflatten_session by focusing on cleanup, not session management.

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?

Provides strong context: when to use (reclaim disk), warns against deleting sidecars if retrieve_flattened is needed, and advises setting include_sidecars=true only when sessions are no longer needed. Does not explicitly mention alternative tools, but the usage is clear.

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