Paper Distill MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: that the tool handles 'full metadata enrichment automatically,' creates 'Zotero journal article items,' and 'maps them to collections based on topic tags.' It also warns about the consequence of not using it ('incomplete metadata'). However, it doesn't mention error handling, rate limits, or authentication requirements.

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 efficiently structured with three focused paragraphs: purpose statement, critical usage guidelines, and implementation details. Every sentence adds value - the first establishes what the tool does, the second provides crucial usage rules, and the third explains the underlying process. No wasted words or redundant information.

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 has an output schema (which handles return values), no annotations, and 100% schema coverage for its single parameter, the description provides strong contextual completeness. It explains the tool's purpose, critical usage rules, and implementation process. The only minor gap is lack of explicit mention of error cases or authentication requirements, but the presence of an output schema reduces the need for return value explanation.

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 100% with the parameter 'paper_ids' well-documented as 'List of paper DOIs or IDs to add to Zotero.' The description adds minimal additional parameter context beyond confirming these are 'IDs/DOIs' and mentioning they come from 'papers.jsonl.' With high schema coverage, the baseline of 3 is appropriate as the schema does most of the parameter documentation work.

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 specific action ('Add papers to Zotero library'), resource ('papers'), and mechanism ('by their IDs/DOIs'). It distinguishes from siblings by specifying it's for adding papers to Zotero rather than other operations like searching, ranking, or managing topics. The description explicitly mentions looking up papers in papers.jsonl and creating Zotero journal article items.

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 provides explicit usage guidance: 'Always use this tool to add papers to Zotero. NEVER call the Zotero Web API directly or generate scripts...' It gives clear alternatives to avoid (direct API calls, scripts) and explains why (incomplete metadata). This is strong positive guidance about when to use this tool versus alternatives.

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