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: it's a write operation (implied by 'collect' and 'save'), has a dependency on prior steps ('latest push'), and includes a strong directive about not using the Zotero API directly. However, it doesn't mention potential side effects like rate limits or authentication needs, leaving some gaps.

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 appropriately sized and front-loaded, with the core purpose in the first sentence and important guidelines following. Every sentence adds value, such as the critical directive and usage timing. It could be slightly more structured (e.g., bullet points), but it remains efficient without 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?

Given the complexity (a write operation with dependencies and sibling tools), no annotations, and an output schema present, the description is mostly complete. It covers purpose, guidelines, and parameter context well. However, it lacks details on behavioral aspects like error handling or output format, which the output schema might address but aren't explained here, leaving minor gaps.

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%, so the baseline is 3. The description adds value by explaining the context of 'paper_indices' ('refer to the latest push') and providing an example ('1,3'), which clarifies usage beyond the schema's technical description. It also hints at the purpose of 'obsidian_mode' by mentioning 'create Obsidian notes,' though it doesn't detail the modes beyond what the schema states.

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 tool's purpose with specific verbs ('collect pushed papers to Zotero') and resources ('papers', 'Zotero', 'Obsidian notes'), and distinguishes it from sibling tools by explicitly mentioning 'collect_to_zotero' as an alternative. It goes beyond a simple restatement of the name by explaining the dual functionality of collecting papers and optionally creating notes.

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 guidance on when to use this tool ('use after finalize_review'), when not to use alternatives ('NEVER call the Zotero API directly'), and names a specific alternative ('collect_to_zotero'). It also includes prerequisites ('paper indices refer to the latest push'), making it comprehensive for agent decision-making.

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