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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond them: a free daily allowance, then $0.002 USDC per call via x402, which tells the agent about throttling and cost before invoking. It does not contradict any annotation.

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?

Two short sentences, both earning their place: the first states the resource and payload, the second states the cost model. The most decision-relevant content is front-loaded.

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 explained, and annotations cover the safety profile. Combined with the pricing disclosure, the definition is nearly complete; only error behavior for invalid or unknown ISSNs is 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?

Schema description coverage is 100% for the single ISSN parameter, so the schema already carries the semantics and baseline 3 applies. The description reinforces that the lookup is keyed by ISSN but adds no format, validation, or normalization detail 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 names the specific resource (journal), the key (ISSN), and the returned fields (title, publisher, DOI counts), which is more than a restatement of the title. It is clearly distinguishable from siblings like crossref__doi or crossref__search, though it does not explicitly name them.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g., valid ISSN format), and no routing to alternatives such as crossref__doi when a DOI is known. The pricing sentence is invocation-relevant but is cost information, not usage guidance.

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