search_works

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds no further behavioral context such as pagination limits, rate limits, or response structure. The description does not contradict annotations.

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 a single sentence that is clear and to the point, with no unnecessary words. It efficiently communicates the core functionality.

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?

For a tool with 11 parameters and an output schema, the description is adequate but incomplete. It mentions key filter types but omits pagination (limit/page), sorting, and peer_reviewed_only. The presence of an output schema reduces the need to explain return values, but parameter usage could be clarified.

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 73% (8/11 parameters have descriptions). The description adds a generic 'and more' but does not elaborate on undocumented parameters like limit, page, or peer_reviewed_only. It provides minimal extra meaning beyond the schema.

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 'Search works in OpenAlex by keyword, filtered by...', providing a specific verb and resource. It distinguishes from sibling tools like fetch_work or fetch_author by focusing on search and filtering, and from semantic_search_works which is a different search method.

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?

No explicit guidance on when to use this tool versus alternatives like semantic_search_works. The description implies usage for keyword-based search with filters but does not specify exclusion criteria or when not to use.

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