arxiv_new

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

The description mentions the return structure but does not disclose any side effects, permissions, rate limits, or error handling. It implies a read-only operation but doesn't explicitly state it.

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 and well-structured, with a summary line followed by clear argument and return sections.

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?

The description covers the main functionality, parameters, and return format. However, it doesn't explain potential pitfalls like pagination limits or the meaning of 'summary' versus 'abstract', leaving some gaps for a complex tool.

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?

The description elaborates on the parameters: category is given with examples (cs.AI, cs.CL, etc.), and limit is defined as 'max papers returned' with a default. This goes beyond the bare 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?

The description clearly states the function: 'Newest arXiv papers in a category' and specifies including title, authors, and abstract. This is unambiguous and distinguishes it from other tools.

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 guidance on when to use this tool versus alternatives is provided. It simply describes what it does without indicating scenarios or comparisons.

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