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

With no annotations, the description carries the full behavioral burden, and it usefully discloses the extraction fallback order, character-offset pagination, and credit cost. However, it omits error behavior, permission requirements, and what happens when none of the fallback content types are available.

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 plus a compact cost tag, with no wasted wording. It presents the core purpose and pagination model immediately.

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 moderate-complexity retrieval tool with no annotations and no output schema, the description covers the return fallback and pagination model adequately. It remains incomplete on limit semantics, error conditions, and authentication or rate-limit context, which are left to inference.

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%, so the description must compensate for all three parameters. It clarifies that pagination uses character offsets and implies paper_id from the purpose, but it does not explain the limit parameter's units or interaction with offset, leaving a meaningful gap.

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 states a specific resource and scope: full text of a paper, with an explicit fallback order of extracted text, OCR markdown, or abstract. It does not explicitly differentiate this tool from siblings such as get_paper or library_get_paper_content, so it is clear but not fully disambiguated.

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?

Usage is only implied by the tool purpose; there is no explicit guidance on when to use this versus sibling retrieval tools. It also does not state when not to use it or what alternatives exist for different paper-content needs.

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