search_works

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

Discloses pagination behavior (cursor vs offset, automatic offset drop). No annotations provided, so description should cover more behavioral traits like rate limits, authentication, or response side effects; these 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?

Concise, well-structured with explanation and three clear examples. No unnecessary information.

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?

Explains core functionality and pagination. With output schema present, return values are covered. Could mention default sort order behavior, but overall sufficient for an 8-parameter 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?

Description explains cursor, offset, filter, sort, order, query, rows, select with examples and conflict behavior. Compensates for 0% schema coverage by adding meaning beyond type/defaults.

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?

Clearly states it searches Crossref works (publications) by free-text query and/or filters. Distinguishes from sibling tools like get_work (DOI lookup) and list_funders.

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 deep pagination with cursor, warns against mixing cursor and offset, and offers examples. Lacks explicit exclusion scenarios (e.g., when to use get_work instead).

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