read_document_page

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is a read (returns text) but does not mention edge cases (e.g., invalid page, unindexed document) or any implicit side effects. For a simple read tool, this is minimally transparent but not rich in behavioral detail.

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 that states the action and outcome with zero filler. It is efficient and immediately informative.

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 tool is simple but the description omits critical context: it does not mention that the document must be indexed (as suggested by the sibling list_indexed_documents), nor does it state the page numbering convention. Without this, an agent might attempt to read an unindexed document or misinterpret page numbers, leading to errors.

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 parameter meaning. It only implies that 'document' identifies a document and 'page' specifies a page number, but does not clarify page indexing (0- or 1-based), expected document ID format, or constraints. This is insufficient given the lack of schema descriptions.

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 action ('Return'), the resource ('complete extracted text of a specific page'), and the target ('document'). It clearly differentiates from siblings: closed_book_search (search) and list_indexed_documents (list), so an agent can distinguish without ambiguity.

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 description provides no guidance on when to use this tool versus closed_book_search or list_indexed_documents. It does not mention that the document must already be indexed or that this tool is for retrieving raw page text rather than searching. An agent is left to infer usage from the tool name.

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