Pubmed Convert Ids

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

Discloses key behaviors: accepts up to 50 IDs, all same type, and only resolves PMC articles. Annotations (readOnlyHint, openWorldHint) are already present, and the description adds relevant constraints. Could mention error handling (e.g., invalid IDs) but still strong.

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 concise sentences, front-loaded with purpose, no redundancy. 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?

Given the output schema's presence, the description covers all necessary aspects: purpose, input constraints, and usage boundaries. Complete for a conversion tool.

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% and both parameters have clear descriptions. The tool description adds overall context but does not significantly enhance parameter understanding beyond the schema.

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: converting between article identifiers (DOI, PMID, PMCID). It also distinguishes from the sibling pubmed_search_articles by specifying the scope (only PMC-indexed 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?

Explicitly tells when to use (for IDs in PMC) and when not to use (articles not in PMC) with a direct 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.