search_records

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

No annotations are provided, so description must disclose behavioral traits. It states it returns a list of record summaries with specific fields, but lacks details on authentication, rate limits, pagination behavior beyond defaults, or error handling. Partially transparent.

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?

Well-structured with clear title, parameter list, and return description. Each sentence adds value; no fluff. Front-loaded with purpose.

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?

Covers purpose, all 12 parameters, and return format. Lacks usage guidance and behavioral context, but for a search tool with no annotations, the description is largely complete. Missing minor details like alternative tool differentiation.

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 adds parameter explanations that are completely missing in the input schema (coverage 0%). Provides meaning and acceptable values for each filter, e.g., resource_type lists possible types. Could be more specific for some string params (e.g., valid community IDs).

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?

Clear verb 'Search' and specific resource 'Zenodo records' with 'rich filtering'. Distinguishes from sibling specialized search tools (e.g., search_by_community) by being the general-purpose search with many filter options.

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 vs alternatives like search_by_community or search_by_funder. The description implies it is the general search but does not mention when to prefer sibling tools.

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