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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the safety profile is free. The description adds genuinely new behavior: the server performs a live arXiv resolution when the paper was not seen this session, and it does not download the PDF — a useful scope boundary and a latency/network hint.

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?

Three short sentences, front-loaded with the core purpose, then field list, then behavioral caveats. No filler, though the field enumeration is somewhat redundant with the output schema.

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?

With an output schema present, return values need not be described, and the description covers the notable non-obvious behavior (session-aware arXiv resolution, no PDF). The only gap is not situating itself against the three sibling tools.

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 single parameter is documented with a concrete example ('2508.19294v2'), so the schema carries the semantics. The description adds nothing about ID format, versioning, or invalid-ID behavior, so the baseline 3 applies.

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?

States a specific verb and resource ('Return detailed metadata for one arXiv paper') and enumerates the fields returned (title, authors, abstract, categories, dates, URLs). This distinguishes it implicitly from the search sibling by scope ('one paper'), though it never names an alternative explicitly.

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?

'Use this for title, authors, abstract, categories, dates, and URLs' gives a context of use, but there is no when-not guidance and no routing to literature_search_papers or literature_retrieve_paper_evidence, which an agent choosing among four siblings would benefit from.

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

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

Beyond the annotations, the description discloses that the PDF is cached in a configured local directory and never overwritten, that extracted pages/chunks live only in server memory, and that repeat calls are safe and reuse the cache. This substantiates the idempotentHint=true and readOnlyHint=false (disk cache write) annotations with concrete mechanics.

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?

Three tight sentences with the action front-loaded and secondary behavioral facts (cache location, memory-only chunks, idempotency) following. No filler or 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?

For a single-parameter, output-schema-backed preparation tool, the description covers the action, the caching side effect, the memory footprint, and repeat-call safety. An agent has everything needed to invoke it correctly and predict its side effects.

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 single arxiv_id parameter is well documented in the schema ('arXiv ID returned by literature_search_papers'). The description adds no syntax, format, or validation detail beyond the schema, so baseline 3 applies.

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?

States a specific three-step verb chain (download, extract, chunk) on a specific resource (one paper) with a stated purpose (evidence retrieval). An agent can distinguish this preparation step from literature_search_papers and literature_retrieve_paper_evidence without opening any schema.

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 phrase 'for evidence retrieval' implies this is a prerequisite for literature_retrieve_paper_evidence, giving implied usage. However, no sibling is named explicitly, and there is no statement of when not to call it (e.g. already-prepared papers) or which tool must precede it.

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

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

Adds real mechanics beyond the annotations: retrieval is local BM25 rather than a model, the paper may be prepared as a side effect, and callers should carry page numbers into the answer. The auto-preparation side effect is consistent with readOnlyHint=false (a read tool that can trigger a write), so there is no contradiction, though failure modes (paper not found, no hits) go unmentioned.

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?

Four short sentences, front-loaded with the action and the pre-condition, then the query-format constraint, then the side effect and the citation obligation. Nothing is redundant or padded.

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?

With annotations present and an output schema covering the return shape, the description supplies the missing operational context: when to call it, how to phrase the query, and the auto-preparation behavior. It omits edge cases such as an unknown arxiv_id or an empty result set, which keeps it just short of complete.

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%, so the baseline is 3, but the description earns credit by explaining *why* the query must be short English keywords (BM25, not a model), which is the rationale the schema omits. The top_k parameter is not addressed in prose beyond the schema's own range documentation.

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?

States a specific verb and resource: retrieving page-cited evidence chunks, scoped to 'one paper', which implicitly separates it from the corpus-wide literature_search_papers sibling. It never names that sibling, so the differentiation is inferable rather than explicit.

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?

"Use this before answering a question about paper content" gives a clear trigger condition, and "the paper is prepared automatically" tells the agent it need not call literature_prepare_paper first. No explicit when-not or named alternative is given, so it stops short of a 5.

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description still earns credit for adding non-annotation context: no PDF download, concise metadata output, and that the returned arXiv IDs are reusable inputs for the sibling tools.

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?

Three short sentences with no filler. The core capability is front-loaded and the routing/exclusion notes follow in priority order.

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?

With an output schema present, return values need no explanation, and the description still sketches what comes back (IDs, metadata) and how to chain it. Nothing an agent needs to call this correctly is missing.

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%, with both query and max_results documented in the schema (including bounds and default), so the baseline is 3. The description adds no syntax, language, or formatting detail for the query parameter beyond what the schema already states.

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?

States a specific verb and resource ("Search arXiv") plus the return shape ("concise paper metadata"). It also positions itself against siblings by telling the agent to use it first when no arXiv ID is supplied, so an agent can distinguish it from literature_get_paper_details and friends without opening a schema.

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?

Explicit routing rule: "Use this first when the user wants literature recommendations or has not supplied an arXiv ID," plus a clear negative ("It does not download PDFs") and a hand-off path (returned IDs pass to the other literature tools). The only gap is that the alternatives are referred to generically rather than named as literature_get_paper_details / literature_prepare_paper.

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