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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the description does not need to restate safety behavior. It adds useful scope about the profile contents and most-cited papers, but it does not discuss authentication needs, rate limits, or error behavior.

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 definition is a single front-loaded sentence that identifies the resource, lookup key, and returned profile contents without filler. Every phrase contributes to understanding what the tool provides.

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?

An output schema exists, annotations cover the safety profile, and the input schema fully documents both parameters, so the description need not explain return structure or permissions in detail. It is complete enough to call correctly, with the main remaining gap being explicit routing guidance versus sibling tools such as search_authors.

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%, and the schema already documents that ORCID may be bare or an orcid.org URL and that papers controls how many most-cited papers are included. The description mentions the ORCID lookup and cited papers, but it adds no parameter meaning beyond what the schema provides.

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 a specific lookup resource and key: one researcher's public profile by ORCID iD, including named fields such as affiliation, topics, metrics, NobleID, and most cited papers. It is clear what the tool returns, but it does not explicitly differentiate itself from the sibling search_authors tool.

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 phrase 'by ORCID iD' implies this tool is used when an ORCID identifier is known, which distinguishes it in practice from broad author searches. However, there is no explicit when-to-use guidance, no exclusions, and no direct reference to search_authors as the alternative for name-based lookup.

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