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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds context about the specific repository (Zenodo) and what is returned (metadata, DOI, file links), going beyond the annotations. However, it does not mention pagination behavior or rate limits.

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 two sentences long, front-loaded with the core purpose, and every phrase adds value. No redundant or vague wording.

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?

With 6 parameters, 1 required, and an output schema, the description covers the key aspects: search domain, query, filters, and return types. It omits explicit mention of pagination (page/size) but the schema examples imply paginated results, so the gap is minor.

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 50%, with descriptions for 'sort', 'type', and 'communities' but none for 'page', 'size', or 'query'. The description clarifies that 'query' is a keyword search and enumerates filter options, partially compensating for missing schema details, but 'page' and 'size' remain unexplained.

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 specifies the tool searches the Zenodo repository for various research outputs by keyword. It explicitly lists filter options (type, community, sort order) and return contents (metadata, DOI, file links), distinguishing it from sibling tools by naming the specific repository and result types.

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 what the tool does but does not provide guidance on when to use it versus alternatives like 'deep_research' or 'search_within'. No explicit exclusion criteria or recommended contexts are given, leaving the agent to infer usage from the description alone.

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