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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds 'no auth required' and names the underlying API (api.crossref.org), which is useful operational context. It does not contradict annotations and provides value beyond them, though it stops short of describing response specifics (covered by output schema).

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 two sentences with no filler. The primary action and fields are front-loaded, followed by use cases and source/auth info. Every sentence earns its place, and it is appropriately sized for a simple lookup tool.

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?

With a single parameter, a comprehensive input schema, an output schema present, and annotations covering safety, the description covers purpose, use cases, data source, and auth. Nothing critical is missing for an agent to correctly invoke and interpret the tool.

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 already documents the single parameter 'issn' with format (NNNN-NNNN) and an example. The description merely restates 'by its ISSN' without adding new semantics or clarifications. Given 100% schema coverage, the baseline of 3 is appropriate; the description adds no extra meaning beyond 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?

The description states a specific verb (Get) and resource (metadata for an academic journal) with a clear input (by ISSN). It enumerates the returned fields (title, publisher, subject areas, DOI coverage counts) and includes the data source, which distinguishes it from sibling tools like crossref.works.search or crossref.funders.search. The purpose is unmistakable and distinct.

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 description offers practical use cases ('verifying a journal's publisher or gauging its publication volume') which imply when to call it. However, it does not explicitly contrast with alternative tools (e.g., doaj.journals.search for name-based lookup) or state when not to use it. Guidance is implied but not explicit, so it does not fully meet the 5-level bar for exclusions and alternatives.

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