get_deepxiv_paper

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

The description states 'Read' indicating a read-only operation, but with no annotations, it fails to disclose other behavioral traits such as authentication requirements, rate limits, or error handling.

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 a single, front-loaded sentence that conveys the essential purpose and available views without unnecessary words. Every element earns its place.

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?

While an output schema exists, the description is minimal and does not elaborate on the differences between views. Given the tool's simplicity, it achieves basic completeness but leaves room for more detail.

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 lists possible values for the 'view' parameter (brief, metadata, preview, raw, json), adding meaning beyond the schema's type-only definition. However, it does not explain what each view returns, and the 'arxiv_id' parameter is left undescribed, partially compensating for 0% schema coverage.

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 specifies the verb 'Read' and the resource 'arXiv paper via DeepXiv', and lists available views (brief, metadata, preview, raw, json), clearly distinguishing it from sibling tools like search_deepxiv or get_deepxiv_pmc.

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 reading an arXiv paper but provides no explicit guidance on when to choose this tool over alternatives (e.g., get_deepxiv_pmc) or when not to use it.

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