Pubmed Convert Ids

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

The description adds constraints beyond annotations (readOnlyHint, openWorldHint) by specifying the PMC-only limitation and batch size. It aligns with readOnlyHint as a safe conversion operation. No contradictions.

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 no wasted words. It front-loads the purpose and immediately provides key constraints and alternatives.

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 presence of an output schema, the description adequately covers purpose, constraints, and alternatives. It does not detail errors or rate limits but is sufficient for a simple conversion tool with good annotations.

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%, so the schema already documents both parameters with examples. The description does not add new parameter details beyond what the schema provides, but it reinforces the single-type constraint and limit, earning a baseline score.

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 converts between article identifiers (DOI, PMID, PMCID). It also distinguishes itself from siblings by specifying it only works for articles indexed in PubMed Central and directs users to pubmed_search_articles for non-PMC 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?

The description provides explicit usage conditions: accepts up to 50 IDs of a single type per request, and resolves only PMC articles. It also tells when not to use this tool and suggests an alternative (pubmed_search_articles).

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