unpaywall_search

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

No annotations are provided, so the description bears the full responsibility. It discloses result limits (50 per page), pagination, and filtering options, but does not mention authentication, rate limits, or output format. With output schema present, return format is covered, but other behavioral traits are missing.

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?

The description is concise and front-loaded with the core purpose. It uses a two-paragraph structure: a brief statement of function and query syntax, followed by an organized Args list. No superfluous content.

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 existence of an output schema, the description adequately covers search behavior, query syntax, pagination, and filtering. It does not mention rate limits or API key requirements, which could be useful. Slightly incomplete but still high.

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 description coverage is 0%, so the description must compensate. It clearly explains each parameter's purpose, type, and default values with examples (e.g., query: 'e.g. "machine learning"', is_oa: 'true = OA only, false = closed only, omit for all', page: '50 results per page, default 1'). This fully compensates for the missing schema descriptions.

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 the tool's purpose: 'Search Unpaywall for scholarly articles by title.' This is a specific verb+resource combination, and it distinguishes from siblings (export and lookup tools) by focusing on search functionality.

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 the query syntax and pagination, giving clear usage context. While it doesn't explicitly compare with siblings, the purpose and features suggest when to use this tool over alternatives. Slight room for more explicit guidance.

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