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 describes key behaviors: extracting keywords from markdown, appending to a JSONL file, and session isolation. However, it doesn't mention important details like whether this is a read-only or write operation, what permissions are needed, error handling, or rate limits.

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 with three focused sentences that each add value. It's front-loaded with the core purpose, followed by implementation details and session management. There's minimal redundancy, though the formatting could be slightly cleaner.

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 moderate complexity, 100% schema coverage, and presence of an output schema, the description is reasonably complete. It explains the core functionality and session isolation well. However, as a tool with no annotations that modifies data (appends to JSONL), it should ideally mention more about the mutation behavior and consequences.

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 schema already fully documents all three parameters. The description mentions 'session_id' and 'search_now' but doesn't add meaningful semantic context beyond what's in the schema descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('ingest', 'extracts keywords', 'appends to interests.jsonl') and resources ('research context from other AI conversations', 'markdown text'). It distinguishes from sibling tools by focusing on context ingestion and keyword extraction rather than paper collection, topic management, or review preparation.

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 clear context for when to use this tool ('Ingest research context from other AI conversations for cross-AI context inheritance') and mentions session isolation to prevent context pollution. However, it doesn't explicitly state when not to use it or name specific alternatives among the many sibling tools.

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