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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Fetch' is consistent with those hints. The description adds useful context about return fields (abstract, authors, journal, MeSH terms), but it does not disclose behavior for invalid/missing IDs, errors, or rate limits, though the schema caps batch size at 200.

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 two sentences with zero waste. The core action and input mode are front-loaded, and the second sentence adds value by summarizing the return payload without unnecessary detail.

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?

For a straightforward fetch-by-ID tool, the description together with the full schema, output schema, and read-only annotations covers the essential invocation requirements. The main gap is the absence of explicit routing to sibling tools for search or full-text retrieval, but this does not prevent correct invocation.

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 documents all three parameters. The description adds marginal value by mentioning MeSH terms, which aligns with includeMesh, but does not explain includeGrants behavior or parameter semantics beyond what the schema 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 states a specific action ('Fetch'), resource ('full article metadata'), and input mode ('by PubMed IDs'), and enumerates key return fields (abstract, authors, journal, MeSH terms). This makes it clear what the tool does and broadly distinguishes it from sibling tools like pubmed_search_articles and pubmed_fetch_fulltext, though it does not explicitly name those alternatives.

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 phrase 'by PubMed IDs' implies a prerequisite, but the description gives no explicit guidance about when to use this tool versus alternatives. It does not direct agents to pubmed_search_articles when IDs are unknown or to pubmed_fetch_fulltext when full text is needed, leaving usage inference to the agent.

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