convert_identifiers

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, any network dependencies, rate limits, or error conditions. The phrase 'through the NCBI ID converter' hints at an external call but does not elaborate. This is insufficient for a tool with no annotation support.

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, concise sentence that communicates the core function efficiently. It is front-loaded and contains no unnecessary words, earning top marks for conciseness and structure.

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?

Although an output schema exists, the description is too sparse for the tool's context. It does not clarify the conversion direction, possible limitations, or what the output represents beyond the schema. The tool has one parameter and no annotations, so the description should carry more contextual weight than it does.

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 has a single 'identifiers' parameter with minimal type info, and the description provides no additional meaning about the parameter—such as acceptable formats, examples, or expected identifier syntax. With schema description coverage at 0%, the description fails to compensate, leaving the agent to guess.

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 uses the specific verb 'Convert' and names the resource 'DOI/PMID/PMCID identifiers through the NCBI ID converter,' clearly stating what the tool does. It lacks an explicit distinction from the sibling tool 'resolve_identifiers,' so it does not fully meet the 'distinguishes from siblings' criterion for a 5.

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?

No guidance is provided on when to use this tool versus alternatives like 'resolve_identifiers' or 'search_literature.' The description simply states the action without any context or exclusionary guidance, so it fails to help an agent decide between similar tools.

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