Paper Distill MCP Server

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it describes the dual return behavior (setup state/config summary vs step-by-step instructions), specifies this is for AI-client interaction ('instructions for the AI client'), and indicates it's a session initialization tool. It doesn't mention authentication needs or rate limits, but covers the core behavior adequately.

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 perfectly front-loaded and efficient: the first sentence states the core purpose, subsequent sentences provide critical usage guidance and behavioral details. Every sentence earns its place with no wasted words, and the structure logically flows from purpose to usage to outcomes.

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 complexity (session initialization with dual behaviors), no annotations, but with an output schema present, the description provides complete context. It explains what the tool does, when to use it, and what to expect in return, making the output schema sufficient for understanding return values without needing description elaboration.

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?

The tool has 0 parameters with 100% schema description coverage, so the baseline would be 3. However, the description adds value by implicitly explaining why there are no parameters: this is a status-checking/initialization tool that doesn't require input. It clarifies the tool's self-contained nature, justifying a score above baseline.

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 ('check setup status', 'guide first-time configuration') and distinguishes it from siblings by focusing on session initialization rather than research tasks like 'search_papers' or 'generate_digest'. It explicitly defines what the tool does in different scenarios (complete vs first run).

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: 'Call this FIRST when starting a new session' establishes clear timing, and it distinguishes when to use this tool versus alternatives by focusing on setup/configuration rather than research operations. The guidance covers both complete and incomplete setup scenarios.

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