cleanup_downloads

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

Beyond the destructiveHint annotation, the description adds critical safety context: it defaults to dry_run so nothing is removed without explicit opt-in, and it requires allow_file_write when dry_run is false. This discloses auth needs and default behavior, going beyond what annotations alone provide.

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 two sentences, front-loaded with the action, and every word earns its place. It avoids fluff while conveying purpose, safety, and permissions.

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?

For a tool with only two simple parameters, an existing output schema is not necessary. However, the description doesn't explicitly state what the dry-run output looks like (e.g., list of files). Still, it covers safety and permission, making it adequately complete for this complexity level.

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 0%, so the description must compensate. It names 'dry_run' and implies 'older_than_days' via 'N days', but doesn't fully explain the parameters or their constraints. The defaults are already in the schema, but the description adds some meaning by explaining the effect of dry_run.

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 function: 'Find or delete files in ~/Downloads older than N days.' It specifies a specific verb (find/delete), a resource (files in ~/Downloads), and a condition (older than N days), making it distinct from sibling tools like delete_file or find_large_files.

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 implies usage for batch cleanup of old downloads but does not explicitly contrast with alternatives or define when not to use it. The dry-run default and permission requirement provide context, but there's no mention of when to prefer this over delete_file or find_large_files.

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