filter_duplicates

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

Discloses the filtering mechanism (DOI match against a file), but no annotations provided, and the description lacks details on side effects (e.g., file modification, network access). Minimal but not misleading.

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?

Single sentence, no fluff, efficiently conveys purpose and mechanism.

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?

Tool is simple with one parameter and an output schema. Description explains what and how, but could mention prerequisite that 'papers.jsonl' must exist. Overall adequate.

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 describes 'papers' as 'List of paper dicts to filter'. Description adds the crucial context that filtering is by DOI match against papers.jsonl, going beyond the schema.

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 the verb 'Remove' and resource 'papers', with specific method 'by DOI match against papers.jsonl'. This distinguishes it from sibling tools like 'collect' and 'collect_to_zotero'.

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?

Implies usage after collecting papers to avoid re-pushing duplicates, but no explicit guidance on when to use vs alternatives or when not to use.

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