pubmed_batch_query

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only mentions context window optimization, but does not explain output structure, error handling, rate limits, or what happens with invalid PMIDs. For a query tool, this is minimal transparency.

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 a single, concise sentence that directly states the tool's purpose, '批量查询多个PMID的详细信息'. It is front-loaded and does not waste words, though it could be slightly more informative without sacrificing conciseness.

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?

With no output schema, the description fails to specify what '详细信息' (detailed information) actually includes or how the output is structured. The 'optimized context window' hint is too vague to be actionable. Given moderate complexity and no annotations, the description is under-specified for an agent to fully rely on.

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 input schema provides 100% description coverage for all three parameters (pmids, query_format, include_abstracts), so the baseline score is 3. The description itself adds no further parameter-specific meaning beyond what the schema already provides.

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 function: '批量查询多个PMID的详细信息' (batch query detailed information for multiple PMIDs). This specifies the verb (query), resource (PMID details), and scope (batch), effectively distinguishing it from siblings like pubmed_get_details (single) and pubmed_batch_download (download).

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 implies a batch use case and mentions 'optimize context window usage', but does not explicitly state when to use this tool over alternatives such as pubmed_get_details or pubmed_quick_search. It lacks explicit exclusions or alternative references, making usage guidance only implicit.

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