arxiv_search

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

No annotations provided, so the description carries full burden. It does not disclose behavior like rate limits, API key requirements, or that results may be outdated due to ArXiv's update schedule. The term 'Great for' is vague and does not clarify operational constraints.

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 concise sentences that front-load the purpose and return format. Every sentence adds value without redundancy.

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 that annotations are absent and output schema is missing, the description provides adequate overview but lacks details on result count limits or pagination. For a simple search tool with 4 parameters, it is minimally complete but could benefit from mentioning max results or behavior when no results found.

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%, and the description adds context by summarizing return fields and intended use for specific domains. However, it does not elaborate on parameter interdependencies or query formatting tips beyond what the schema provides. Baseline 3 is raised to 4 due to additional context about return values.

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 starts with a clear action verb 'Search' and specifies the resource 'ArXiv for academic papers and preprints'. It lists return fields (title, authors, abstract summary, PDF link, categories) and mentions target domains (CS, ML, physics, mathematics), which helps differentiate from sibling search tools like bazaar_search or devto_search.

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 cutting-edge research in specific fields, but provides no explicit guidance on when to use this tool versus alternatives like semantic_scholar_search. No mention of when not to use it or prerequisites.

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