Cleanup Session Images

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds context about automatic cleanup but does not disclose further behavioral traits such as confirmation requirements or effects on other users. Given annotations, the description provides adequate but not rich behavioral context.

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 with no wasted words. The first sentence states the primary purpose, and the second provides usage guidance. Highly efficient and front-loaded.

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 tool's low complexity (2 optional params, no output schema) and annotations covering destructive and idempotent traits, the description covers purpose, usage frequency, and a parameter hint. It does not describe return behavior, but this is a minor omission for a simple cleanup tool.

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 coverage is 100%. The description adds meaning for the 'all' parameter ('use all=true to purge all sessions'), but does not enhance understanding of 'older_than_minutes' beyond the schema. With full coverage, baseline is 3.

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 'Deletes temporary ClipSnap images from the session temp directory' using a specific verb and resource, and distinguishes itself from automatic cleanup, which effectively differentiates it from the sibling tool 'paste_recent'.

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 states 'Automatic cleanup already runs on TTL/size limits, so this is rarely needed', providing clear guidance on when to use this tool versus relying on automatic cleanup. Also advises using 'all=true' for purging all sessions.

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