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

With no annotations, the description carries the full burden and delivers: it discloses output format (text extracted, page-numbered as [Page N]), a critical truncation behavior for long papers, and the recovery path (re-call with start_page/end_page). This is exactly the behavioral context an agent needs and cannot get from the schema.

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?

Front-loaded with the core action, then usage, then discovery guidance, then the truncation caveat. Four sentences, each carrying distinct information with no 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?

An output schema exists, so return-structure explanation is unnecessary. Given that, the description covers the essentials: scope, discovery prerequisite, truncation, and continuation. Nothing an agent needs to call it 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 coverage is 0%, so the description must compensate; it explains the purpose of start_page/end_page (continuing a truncated read) and contextualizes paper_id via the search-first guidance. It stops short of describing units, ranges, or defaults for the page params, leaving some gaps.

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 (Read) and resource (full text of a paper in the user's own paper library / uploaded PDFs), and clearly distinguishes this from the discovery siblings (search_papers, list_papers) by naming paper_id as the input it needs.

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 when-to-use ('answer questions about a specific paper the user uploaded') and a named alternative with its triggering condition ('Call search_my_papers first when you only know a topic/title, not the paper id'). Nothing is left to inference about routing.

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