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

No annotations are provided, so the description must carry the full burden. It only says 'search' - it does not disclose whether the search is read-only (likely), any rate limits, or what kind of results are returned (e.g., metadata, full-text, links). The minimalism leaves the agent without safety or operational context.

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 extremely brief and front-loaded, having no filler. However, it is under-specified rather than concise: a single sentence that omits crucial details. It is not bloated, but it does not earn its place by adding value beyond the name.

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?

Despite having an output schema (which might partially compensate), the description gives no guidance on how to shape the query, what kinds of records are included, or any limitations. For a search tool among hundreds of siblings, more context is needed to avoid misinvocation (e.g., does it require a query, what happens with empty q?).

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 explain parameter meanings. It mentions 'q' implicitly as the search query but adds no details about expected format (e.g., boolean operators, fielded search, quotes). The description is insufficient to guide proper query construction.

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 states a specific verb ('search') and resource ('Zenodo open-research records'), which is clear enough to distinguish from unrelated tools. It does not explicitly name siblings like 'datacite' or 'doi' that might be alternatives, but the purpose is unambiguous.

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 usage (searching Zenodo records), but does not specify when to prefer this over other academic/research tools (e.g., 'arxiv', 'datacite'). There is no explicit guidance on when not to use it or mention of alternatives, leaving the agent to infer.

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