arxiv_search

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

Annotations indicate readOnlyHint=true and idempotentHint=true. The description adds that queries are auto-prefixed with 'all:' and that setting 'days' changes sorting from relevance to submission date, providing behavioral details beyond the 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?

Three concise sentences: first states purpose, second explains query syntax, third covers 'days' effect. No unnecessary words, well-structured for quick scanning.

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 tool's complexity (arXiv API syntax) and presence of output schema, the description covers essential usage info: query types, parameter effects, and sorting behavior. It is sufficient for an agent to use effectively without missing critical details.

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?

With 0% schema description coverage, the description compensates by explaining the 'query' parameter syntax, the 'days' parameter's cutoff and sorting effect, and implies 'max_results' default. The 'response_format' parameter is not discussed but has an enum in 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?

Description clearly states 'Search arXiv' and explains query syntax, distinguishing it from sibling tools like arxiv_recent which likely focuses on recent papers. The specific mention of auto-prefixed 'all:' and field syntax clarifies the tool's exact function.

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 explicit guidance on when to use plain keywords vs. advanced arXiv field syntax, and explains the effect of the 'days' parameter on sorting. While it doesn't explicitly mention alternatives, the behavior is well-described.

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