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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds the field inventory (including the conditional ARK behavior 'when the paper has a confirmed NobleID'), but says nothing about failure modes such as an unresolved identifier.

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?

A single front-loaded sentence with the verb and resource first, followed by the field list. No wasted sentences, though the enumerated field list is somewhat dense for one sentence.

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, so return values need not be re-explained, and the one parameter is fully documented in the schema. The only real gap is routing guidance relative to sibling tools, which keeps it off a 5.

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 identifier schema itself documents all five accepted formats (NobleBlocks id, DOI, ARK, OpenAlex W-id, pmid:), so the description needn't compensate. Baseline 3 is the right ceiling here.

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?

States a specific verb+resource ('Get full metadata for one paper') and enumerates the returned fields, which clearly separates it from search_papers. It does not name or contrast with the siblings get_citation/search_papers explicitly, so it falls short of 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 statement of when to use this tool versus search_papers or get_citation, and no prerequisite guidance (e.g., that search_papers is how you obtain the NobleBlocks id). Usage is only implied by 'one paper'.

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