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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the return is the 'complete text' of a single page, which is useful scope information, but says nothing about invalid/out-of-range page handling or result size limits.

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?

Two tight sentences with zero filler, and the core action is front-loaded before the usage hint.

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 two-parameter read-only retrieval tool with no output schema, the description is adequate but leaves the document identifier format and page-boundary behavior unexplained—the exact details an agent needs to avoid a failed call.

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 schema documents only that 'document' is a string and 'page' is an integer. The description implies a page number within a PDF source, but does not clarify the document identifier format (name vs. ID) or whether page numbering is zero- or one-based, leaving required parameters under-specified.

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 (Retrieve), resource (complete text of one page), and scope (from a PDF source document). An agent can immediately distinguish this single-page retrieval from the broader search_knowledge and the listing-oriented list_documents sibling.

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?

Explicitly names the triggering tool and condition: 'Use this after search_knowledge() when more context or source verification is needed.' This gives clear routing context, though it does not state when NOT to use it or how it relates to list_documents.

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