cleanup_scans

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

The description discloses key behavioral traits: it keeps the N most recent scans, deletes everything older, and performs cascade deletion. With no annotations provided, this fully compensates by detailing the mutation and data removal behavior.

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?

The description is concise with three sentences plus structured Args/Returns sections. It is front-loaded with the main purpose and behavior, making it efficient and easy to parse.

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 one simple parameter and an existing output schema, the description is complete. It covers purpose, behavior, parameter details, and return value, leaving no apparent gaps.

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?

The description adds meaning beyond the input schema: 'Number of most recent scans to keep (default 5, min 1).' The schema only provides type and default, so the description clarifies the parameter's semantics and adds a constraint.

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 the tool's purpose: 'Remove older scans from the database to free up space.' This is a specific verb-resource combination that distinguishes it from sibling tools like list_scans or scan_disk.

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?

The description explains the behavior (keeps N most recent scans, deletes older) and mentions cascade deletion. While it doesn't explicitly state when to use vs. not use alternatives, the context is clear enough for an agent to infer usage scenarios.

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