remove_duplicates

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

With no annotations provided, the description carries full responsibility. It discloses the destructive nature (removes duplicates) and the preview option (dry_run). This is sufficient for a simple tool. It does not mention reversibility or impact on other bookmarks, but the behavior is clearly summarized.

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 concise sentences with no unnecessary words. The first sentence states the action and its effect, and the second provides a key usage guideline. Every part earns its place.

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 simplicity (one optional parameter, no output schema), the description covers the essential aspects: what it does, how to preview, and the default behavior. It could mention that the operation is irreversible without dry_run, but it is largely complete.

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 schema only defines a boolean dry_run parameter with no description. The description compensates by explaining its purpose ('to preview without deleting'), adding meaning beyond the schema structure. With 0% schema description coverage, this is valuable.

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 action ('Remove duplicate-URL bookmarks') and the resource ('bookmarks'). It specifies the behavior of keeping the first in each group, which distinguishes it from sibling tools like find_duplicates (which only identifies) and remove_bookmark (which removes a single bookmark).

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 includes a usage hint for the dry_run parameter ('Use dry_run=true to preview without deleting'), which helps agents use the tool safely. However, it does not explicitly state when to use this tool versus alternatives like find_duplicates (e.g., to preview before deletion) or provide conditions for not using it.

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