Sweep scratch leftovers (loop hygiene)

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

Adds extensive behavioral context beyond annotations: dry-run default, matching criteria, deletion safety checks, and permanent vs restorable deletes. Contradicts nothing in annotations.

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?

Three well-organized paragraphs, each serving a purpose. No redundancy, all sentences add value. Could be slightly more concise but acceptable given depth.

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 no output schema, description covers dry-run report contents and deletion behavior comprehensively. Covers standard use cases. Missing pagination or performance notes, but adequate for tool complexity.

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%, so baseline is 3. Description adds extra meaning: explanations of default values, behavior of confirm, and conditions for deletion. Compensates with richer context.

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 identifies the tool as scanning for disposable records by specific naming/tag conventions. It explicitly states the verb 'sweep' and the resource 'scratch leftovers', distinguishing it from siblings (no other sweep 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?

Provides clear when-to-use guidance: for cleaning up temporary records from loops. Mentions dry-run default, confirm=true for actual deletion, and safety checks. Implicitly contrasts with delete_resource by referencing 'same gated delete path'. Lacks explicit when-not-to-use, but context is strong.

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