search_unpaywall

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

Discloses that the tool extracts the first DOI from the query, returns at most one record, and that max_results is kept for consistency with no effect. Return format is described as a list with one dict or empty.

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?

Concise, well-structured with Args and Returns sections. Every sentence adds value without redundancy.

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?

The tool is simple, and the description covers all critical aspects: purpose, parameters, behavioral quirks, and output format. No gaps given the context.

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?

With 0% schema description coverage, the description compensates by explaining that 'query' can be a DOI string or text containing a DOI, and that 'max_results' is for API consistency but always returns one record.

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 clearly states it looks up a DOI via Unpaywall and returns OA metadata, distinguishing it from generic keyword searches (e.g., search_arxiv). It specifies the exact resource and action.

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?

Explicitly notes that Unpaywall does not support generic keyword search, guiding when not to use. It does not name direct alternatives but provides clear context for appropriate use.

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