search_papers_tool

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

Describes the two backend behaviors, sort limitations, and return format (formatted string). With no annotations, this is adequate but lacks details on rate limits or authentication.

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 single paragraph with no redundancy. All sentences add value, though a bulleted list could improve readability.

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?

Given the tool's complexity (two backends, sort options) and no visible output schema, the description is fairly complete but the return format ('formatted string') is vague.

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 sort_by values and use_scopus behavior, and provides a query example. However, the 'limit' parameter is not explained.

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 searches for papers using Scopus or OpenAlex, with specific mention of standard and advanced syntax. However, it does not explicitly differentiate from sibling search tools like search_papers_s2_tool.

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 guidance on when to use OpenAlex vs Scopus (e.g., for open access PDF links) and notes sort_by only works with OpenAlex. But no explicit comparison to alternatives or in which scenarios to prefer this tool over siblings.

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