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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description only needs to add context. It discloses the structure of results (DOI, title, creators, etc.) and mentions CC0 licensing, which is useful. However, it does not discuss pagination or rate limits, though those are covered by the schema and 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 efficiently front-loaded with the core purpose, then details filters, sorting, and result fields. The closing background on CERN/OpenAIRE is slightly extraneous but not excessive; it remains focused and reasonably concise.

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 rich schema (all parameters described) and safety annotations, the description provides sufficient context for an agent to select and invoke the tool correctly. It covers what is searched, how to filter/sort, and what results contain. It could mention related Zenodo tools for navigation, but this is not critical for its standalone use.

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 100%, so the baseline is 3. The description provides a high-level summary of filterable fields and sort orders but adds little beyond what the schema already documents. It does not introduce new parameter details or examples beyond those present in 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 the tool's function—searching Zenodo's 3.5M+ research outputs—and lists content types, filters, and sort options. It distinguishes itself from sibling tools like zenodo.records.detail and zenodo.records.files by focusing on search, though it does not name them explicitly.

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 implies use for searching Zenodo's repository but does not explicitly state when to prefer this tool over alternatives like openaire.products.search or other record detail tools. There are no exclusions or alternative recommendations, leaving the agent to infer usage from the purpose alone.

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