Paperlib MCP

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 mentions 'Async Parallel' and concurrency details, which is useful. However, it doesn't disclose critical behavioral traits: whether this is a read-only or write operation (though '写入' suggests writing), what permissions are needed, whether it's idempotent, error handling, rate limits beyond concurrency hints, or what happens during a 'dry_run'. For a tool with 8 parameters and no annotation coverage, this is insufficient.

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 concise with three sentences: purpose statement, parallel processing note, and concurrency parameter explanation. It's front-loaded with the core functionality. However, the 'Args:' section formatting is slightly inconsistent with the rest, and some sentences could be more polished, but overall it's efficient with minimal waste.

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 (8 parameters, no annotations, but has output schema), the description is incomplete. It lacks behavioral context for a write operation, doesn't explain most parameters, and provides minimal guidance on when to use it. While the output schema might cover return values, the description doesn't address prerequisites, error conditions, or integration with sibling tools, leaving significant gaps for agent understanding.

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 0%, so the description must compensate for all 8 undocumented parameters. It only explains one parameter ('concurrency') with some detail, briefly mentions 'chunks' contextually, but ignores the other 7 parameters (doc_id, chunk_ids, mode, max_chunks, llm_model, min_confidence, dry_run). This leaves most parameters semantically unclear, failing to adequately compensate for the schema gap.

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: '从文档的 chunks 中抽取实体、关系和结论，写入 GraphRAG 表' (extract entities, relationships, and conclusions from document chunks and write to GraphRAG table). This specifies the verb (extract/write), resource (document chunks/GraphRAG table), and scope (entities, relationships, conclusions). However, it doesn't explicitly differentiate from sibling tools like 'extract_graph_missing' or 'canonicalize_entities_v1', which prevents a perfect score.

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 some usage context: '使用并行处理以加快速度' (use parallel processing to speed up) and mentions OpenRouter's high concurrency support. However, it doesn't explicitly state when to use this tool versus alternatives like 'extract_graph_missing' or 'canonicalize_entities_v1', nor does it provide exclusion criteria or prerequisites. The guidance is implied rather than explicit.

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