Pubmed Europepmc Fetch

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

Adds behavioral context beyond annotations: full abstract retrieval, handling of truncation, and support for non-PubMed records. No contradiction with readOnlyHint or openWorldHint.

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?

Each sentence serves a distinct role: purpose, linkage to search, sibling exclusion, limit. No fluff. Front-loaded with the core action.

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 (array parameter, output schema exists), the description covers retrieval path, truncation handling, source-specific quirks, and alternatives. Leaves no obvious gaps for the intended use case.

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 coverage is 100%, but description adds crucial nuance: instructs to copy epmcId from search results, explains source enum meanings (e.g., PMC returns canonical MED record with pmcId), and clarifies the need for both params. This goes beyond schema definitions.

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?

Clearly states the action (fetch records including full abstract) and the resource (Europe PMC records addressed by source and epmcId). Distinguishes from sibling tools like pubmed_europepmc_search and mentions specific record types (PPR, PAT, AGR).

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?

Explicitly explains when to use this tool (after pubmed_europepmc_search returns truncated abstracts) and when not to (for records with PMID/DOI, use other tools). Provides batch limit of 25 records per call.

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