Read paper as markdown

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

The description discloses pagination behavior and the markdown_path cache file, which can be Read/Grep'd directly—information not captured by annotations. It also explains the download/convert process, adding meaningful behavioral context beyond the readOnly/idempotent hints.

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?

Two sentences, front-loaded with the core action and a practical tip about the cached file. Zero redundant 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?

The description covers the tool's full flow—download, convert, return text, and cache file—and the existing output schema handles return details. It lacks explicit fallback/error context (e.g., if conversion fails), but that's not essential given the output schema.

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 coverage is 100%, with each parameter already described in detail (e.g., arxiv_id resolves versionless IDs to latest, offset is character offset). The description's 'paginated' mention aligns with offset/max_chars but doesn't add meaning beyond the schema; baseline 3 is appropriate.

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 action: 'Download an arXiv paper, convert it to markdown, and return its text (paginated).' This distinguishes it from siblings like search_papers (search) and get_paper (likely metadata), making the tool's purpose unmistakable.

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?

It provides clear context: the tool returns paginated text and also a markdown_path for full-text access, suggesting when to use the cached file instead of paging. However, it doesn't explicitly contrast with sibling tools like get_paper or define exclusions.

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