Pubmed Convert Ids

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

The description adds behavioral traits beyond annotations: it specifies the PMC-only constraint and the batch size limit. No contradiction with annotations (readOnlyHint and 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?

The description is three sentences, front-loaded with purpose, then constraints and alternatives. Every sentence earns its place with no wasted words.

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 is a simple conversion tool with two parameters and an output schema, the description is complete. It covers purpose, usage guidelines, constraints, and alternatives. The presence of an output schema reduces the need to explain return values.

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%, but the description adds meaningful examples for IDs (DOIs, PMIDs, PMCIDs) and clarifies that the 'PMC' prefix is optional. For idType, it explains why it is required, adding value 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 states 'Convert between article identifiers (DOI, PMID, PMCID)', which is a specific verb (convert) and resource (article identifiers). It clearly distinguishes itself from sibling tools like 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?

The description explicitly states when to use this tool ('Only resolves articles indexed in PubMed Central') and when not to, providing an alternative ('for articles not in PMC, use pubmed_search_articles instead'). Also mentions the batch limit of up to 50 IDs of a single type.

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