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

readOnlyHint=true already covers the safety profile, and the description adds genuine behavioral context by disclosing the returned payload (title, author, abstract, keywords, publish date, SHA-256 fingerprint, blockchain proof) in the absence of an output schema. It does not cover failure behavior for an unknown slug, which is the remaining gap.

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 returned-field enumeration folded in; no wasted words and everything the agent needs is at the start.

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?

For a one-parameter read tool with readOnlyHint and no output schema, the description compensates well by enumerating the response fields. Only error/not-found behavior is left unaddressed.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains that slug comes from search_papers. The description adds no further format or validation detail, making the baseline 3 correct.

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 and resource ('Get one World Innovation paper') and enumerates what a paper record contains, so the agent knows exactly what comes back. It implicitly distinguishes itself from search_papers by scoping to a single paper, but never names the sibling explicitly.

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?

Usage is only implied: 'one ... paper' suggests a detail fetch rather than a search, and the slug description in the schema ('Paper slug from search_papers') hints at the search-then-fetch flow. The description itself gives no when-to-use, prerequisites, or alternatives among cite_paper/verify_paper.

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