dedupe_folder

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

With no annotations, the description carries the full burden. 'Never deletes files' is a genuinely useful and non-obvious disclosure given the dedupe name, but it omits whether the tool is read-only, what permissions are needed, and what the output looks like.

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 tight sentences, front-loaded with the core action and followed by the key safety constraint. No wasted words.

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?

A four-parameter tool with no output schema and no annotations needs more than two sentences. The threshold value, candidate cap behavior, and return shape are entirely unexplained, leaving the agent under-informed for correct invocation.

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 only 25% (just 'folder'); the description adds no meaning for recursive, threshold, or max_candidates, leaving three parameters undocumented in both places. It does not compensate for the coverage gap.

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?

States a specific verb and resource: groups exact SHA-256 duplicates and lists near-duplicate candidates in a folder. The scope is unambiguous, though it does not distinguish itself from the sibling analyze_file.

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?

Usage is implied by the description (scanning a folder for duplicates), and 'Never deletes files' hints at safety, but there is no explicit when-to-use, when-not-to-use, or alternative routing versus analyze_file.

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