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

Annotations already declare openWorldHint=true and destructiveHint=false, but the description adds the crucial fact that each successful call costs $0.003 USDC on Base via x402, which explains the non-readOnly/ non-idempotent hints. It still omits failure/refund behavior and rate limits, so it is helpful but not exhaustive.

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?

It is one dense sentence plus a use-case sentence, front-loaded with what is searched and what is returned before the filters and cost. Nothing is wasted, though the return-field enumeration makes the opening clause long.

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 usefully lists return fields (title, authors, year, venue, citation count, DOI, abstract) and covers filters, result cap and payment cost. It lacks only edge-case behavior for an obviously simple query tool.

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 query, limit and fromYear are already documented in the schema with ranges and defaults. The description only restates the fromYear filter and the 20-result cap, adding no syntax or format detail beyond the schema baseline.

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 a specific verb (search) plus the resource and its scope (scholarly literature across journals, conferences, preprints and books) and even enumerates the returned fields. No sibling tool covers literature search, so an agent can select this unambiguously.

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 concrete when-to-use contexts: research agents, literature reviews, fact-checking a claim against published work, and finding a DOI for a citation. It stops short of naming when NOT to use it or an alternative tool, but no sibling overlaps this capability.

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