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

Annotations already cover read-only/open-world/idempotent, and the description adds substantial value on top: exact price, the 402-challenge payment handshake, the note that 404s and >=400 failures are not charged, the 1,200-char abstract cap, and the auto-pay npm package. These are precisely the behavioral traits an agent needs before invoking a paid call.

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?

Long but dense with distinct facts (price, sources, return fields, filters, payment flow, billing rules), and the PAID/cost header is front-loaded. A couple of clauses about the payment flow and fiatdock-mcp could be trimmed, but nearly every sentence earns its place.

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?

Covers purpose, source coverage, return content, filter/sort semantics, and the full payment lifecycle. An output schema exists so return-value explanation is not strictly required, and the parameter schema is fully documented. Nothing an agent needs to call this correctly is missing.

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 baseline is 3, but the description adds meaning beyond the schema — that citation and date sorts match title and abstract so results stay on topic, and that an empty query searches the published example. It goes slightly beyond restating the schema fields.

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?

Opens with a specific verb+resource ('Search the scholarly literature') and names both upstream sources (OpenAlex ~250M works, Crossref fallback). It enumerates return fields and available filters, so an agent knows exactly what the tool produces without opening the schema. No sibling competes for this purpose.

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 explains sorting defaults and the Crossref fallback, but those are internal behaviors rather than guidance on when to choose this tool over an alternative. With no sibling offering academic search, there is nothing to route against, yet there is no explicit 'use this when…' framing either. Usage context is implied rather than stated.

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