zotero_find_duplicates

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

No annotations provided, so description fully discloses behavior: read-only, works in local/web mode, O(n²) complexity, returns markdown blocks with keys/titles/DOIs/dateAdded, does not merge. Transparent about limitations and side effects.

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?

Description is fairly dense but each sentence adds value. Front-loaded with main purpose. Could be slightly trimmed, but no wasted words. Example and details are justified.

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 output schema exists (context true), description explains return format (markdown per group) and how to use results. Covers complexity, usage, alternative tools, and limitations. Complete for tool's 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 has 0% description coverage, but description explains all three parameters in detail: method with enum options explained, collection_key with purpose and default, limit with default. Also relates collection_key to library size cap.

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?

Description clearly states it scans for duplicate items and returns candidate groups for review. It explicitly distinguishes from zotero_merge_duplicates by noting it only identifies duplicates, not merges. Provides specific verb 'scan' and resource 'active library or collection'.

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?

Explicitly states when to use each method (e.g., prefer 'doi' for unattended merge), when to use collection_key (for large libraries), and warns about library size cap. Gives example call. Provides clear guidance on when not to use without collection_key for large libraries.

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