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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds genuinely non-obvious behavior: 50-row paging, empty pages, and uncertain continuation on a full page. The offset/resultOffset interplay is stated but in dense, hard-to-parse prose that stops short of explaining why the two offsets differ.

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?

Four sentences, front-loaded with the core purpose and no filler. The second sentence is jargon-heavy ('Consume nextResultOffset within the same upstream offset...') and costs more parse effort than its length suggests.

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 no explanation, and the description covers the ingestion path, the no-accepted-ID case, and the paging edge case. What remains unaddressed is why two offset parameters coexist, which is the one thing an agent is most likely to get wrong.

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; the description earns an extra point by explaining the relationship between resultOffset and the upstream offset, which the schema documents only in isolation. It does not, however, clarify the syntax of the ID forms beyond what the schema already spells out.

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 (retrieve) and resource (synonyms) tied to a precise input (an AphiaID from worms_resolve_taxon), and implicitly distinguishes itself from worms_get_taxon, which is named for the contrasting case. An agent can tell what this returns without opening the schema.

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?

Gives an explicit exclusion ('A present name without an accepted ID has no synonym lookup') plus the alternative to use instead (worms_get_taxon), and prescribes a pagination protocol ordering nextResultOffset consumption ahead of advancing page.nextOffset. Both when-to-use and when-not-to-use are covered.

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