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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it explains that full-text records include conditions/measurements/results/limitations and that totals are included so a capped list is not mistaken for the whole paper. No contradiction with annotations.

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?

One dense, well-structured sentence front-loads the core purpose ('one paper's compiled record') before itemizing contents. Every clause contributes information about what the agent will receive, with no filler or repetition of schema details.

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 and strong annotations, the description provides sufficient detail about packet composition and the full-text vs. non-full-text distinction. It lacks explicit sibling differentiation, but that gap is more about usage guidance than completeness for invoking this 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?

Schema coverage is 100% and the schema already describes arxiv_id formats and the limit range, giving a baseline of 3. The description adds value by tying the limit behavior to the packet's capped lists and explaining that totals prevent misinterpretation, which clarifies what the limit parameter actually controls.

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 identifies the tool as returning one paper's compiled record and enumerates the packet contents: the authors' claim/contribution, abstract sentence roles and probabilities, paper-level labels, and full-text evidence. It goes well beyond the title, though it does not explicitly contrast itself against siblings like get_record or paper_bridge.

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 'small enough to hold beside others' and the detailed contents imply this is for reading and comparing compact per-paper records, but there is no explicit when-to-use/when-not-to-use guidance or named alternatives. Usage context is present only by implication.

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