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

Goes well beyond the readOnly/openWorld annotations: it discloses that the source is a public REST API with no key, that unknown DOIs produce 404, that each successful call costs $0.002 in USDC via x402 on Base/Solana/Arc, and that failed calls are free. The only omission is latency/rate-limit behavior for a paid tool.

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?

Three dense clauses front-load the resource and return shape, then error semantics, then price. Every sentence carries information, though packing the pricing/payment rail detail into the same breath as the data fields makes it slightly dense to scan.

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 single-parameter read with annotations and an output schema present, the definition covers what an agent needs: the data returned, the failure mode, and the cost. A brief pointer to search_crossref as the alternative would close the only real gap.

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?

With a single required parameter at 100% schema description coverage (including a DOI example), the baseline is 4. The description correctly frames the parameter as identifying exactly one paper rather than adding redundant format detail already present in the schema.

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 ('Crossref DOI lookup') and scopes it to 'one paper', which differentiates it from a bulk/list search. It does not name the near-identical sibling search_crossref, so the agent must infer which to call from position alone.

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 implicit trigger (you already have a DOI) is clear from 'DOI lookup ... for one paper', and the 404 behavior on unknown DOIs is stated. However, there is no explicit when-not guidance and no mention of the obvious alternative (search_crossref), leaving the sibling choice ambiguous.

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