journal_metrics

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context by enumerating the return payload (since there is no output schema) and noting that exact ISSN lookups collapse to a single result while name searches can return up to `limit`. It does not describe what happens on no-match or ambiguous name matches, which is the main 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?

Two sentences, both front-loaded: the first delivers purpose plus return shape, the second delivers accepted inputs plus the chaining hint. The long metric enumeration earns its space because there is no output schema to carry it.

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 no output schema, the description carries the full burden of explaining returns and does so thoroughly, and both parameters are covered. It is not fully complete because match-ambiguity behavior and failure modes for an unrecognized journal are unstated, which matters for a read-only open-world lookup.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the schema by noting that ISSNs live on article records (a data-source hint absent from the property description) and by clarifying the accepted identifier classes. The `limit` semantics are restated rather than extended, so it is not a full 5.

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 opens with a precise verb+resource framing ('Journal quality metrics') and immediately enumerates what is returned: OpenAlex 2-year mean citedness, h-index, i10-index, citation counts, is_oa, and quality-list tiers. It also positions the tool relative to the well-known Clarivate impact factor, so an agent knows exactly what this produces and how it differs from a familiar alternative.

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?

It gives a concrete workflow hint that no sibling tool offers: ISSN input can be sourced from 'article records carry journal_issn', which tells an agent how to chain this from article_search/article_get. What it does not do is state when-not to use it or name any sibling alternative, so it falls short of the full when/when-not/alternatives bar.

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