Pubmed Fetch Articles

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds no extra behavioral context such as rate limits, authentication, or what happens with invalid IDs. It simply restates the operation.

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?

Two sentences, no redundancy. Front-loaded with key action and output. Every word adds value.

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 an output schema present, description adequately covers the tool's return value. It could be improved by mentioning error cases or pagination, but for a straightforward fetch tool with 3 params, it suffices.

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?

Input schema has 100% description coverage, so description does not need to explain parameters. The description adds marginal value by listing return fields (abstract, authors, etc.), which indirectly relates to includeMesh parameter but doesn't elaborate on parameter specifics.

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?

Description clearly states the verb ('Fetch'), resource ('full article metadata'), and input ('by PubMed IDs'). It lists key return fields (abstract, authors, journal, MeSH terms), distinguishing it from siblings like pubmed_fetch_fulltext or pubmed_search_articles.

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?

Description implies usage for fetching metadata by IDs but provides no explicit guidance on when to use versus alternatives (e.g., pubmed_fetch_fulltext for full text) or when not to use. No context on prerequisites or exclusions.

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