arxiv_recent

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

Annotations declare readOnlyHint=true, and the description adds that results are sorted by submission date (newest first) and 'days' filters by published date. This goes beyond annotations to clarify sorting and filtering behavior. No contradictions with 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?

The description is concise (two sentences plus a list of categories), front-loading the purpose. The category list adds value but slightly lengthens it. Overall, efficient with no wasted words.

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 4 parameters, 1 required, and an output schema, the description covers core functionality but omits explanations for 'max_results' and 'response_format'. It does not mention rate limits or result interpretation, leaving some contextual gaps.

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%, but the description explains 'days' (filters by published date) and provides a list of common categories for 'category'. However, 'max_results' and 'response_format' are not explained, leaving gaps in parameter understanding.

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 states 'Fetch recent arXiv papers in a category, sorted by submission date (newest first).' This provides a specific verb (fetch), resource (recent arXiv papers), and distinguishing detail (sorted by date), differentiating it from sibling arxiv_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 explains the 'days' parameter filters by published date and lists common categories, but lacks explicit guidance on when to use this tool vs alternatives like arxiv_search. No when-not-to-use or alternative suggestions are provided.

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