convert_ids

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

The description mentions the NCBI ID Converter API, offering a bit of external context, but it does not disclose response format, error behavior, or rate limits. With no annotations, the description carries the full burden, yet it only covers the basic conversion functionality.

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 a single sentence that is direct and front-loaded, with no wasted words. It efficiently conveys the tool's core purpose.

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's simplicity and well-specified schema, the description is adequate for an agent to understand its function. It does not explain return format, but the purpose is unambiguous and the schema covers operational details like batch limits.

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?

The input schema fully describes each parameter with enums and descriptions, covering 100% of parameters. The description adds no additional meaning beyond naming the supported identifier types, which the schema already enumerates.

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 PMID, PMCID, and DOI identifiers, specifying the verb 'Convert' and the resource. It distinguishes itself from sibling tools that fetch or search articles rather than convert ID types.

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 makes the tool's purpose evident and gives context for when to use it, but it does not explicitly state when not to use it or name alternative tools. The differentiation from siblings is implicit rather than explicit.

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