get_journal_metrics

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the primary data source (Scopus Serial Title API) and the automatic fallback to a bundled Scimago table when it is unavailable. It omits auth requirements, rate limits, and latency, 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?

Three short sentences, each earning its place: what comes back, how it is sourced, and how to get the input. The payload is front-loaded ahead of the sourcing and prerequisite details.

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?

No output schema exists, and the description compensates by enumerating the returned metrics (quartile, CiteScore, SJR, SNIP). Combined with the source/fallback note and the ISSN sourcing hint, an agent has enough to call it correctly for a one-parameter tool; finer details like response shape per category are left implicit.

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?

Single parameter with 100% schema description coverage, so the schema already explains the ISSN format with an example. The description says the input is an ISSN (and implicitly points at sources for it) but adds no format nuance beyond the schema. Baseline 3 applies.

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?

Names a specific resource (journal quality metrics for an ISSN) and enumerates exactly what comes back — quartile per subject category, CiteScore, SJR, SNIP. It is clearly distinguishable from siblings like search_scopus or get_author_profile. It lacks an explicit verb, but the resource and payload are unambiguous.

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?

Provides real routing guidance: it tells the agent where to obtain the required ISSN (search_scopus or get_abstract_details), which is the main precondition for calling it. It stops short of stating when NOT to use the tool or what to do if no metric exists for an ISSN.

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