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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only states the core action (extracting text) but does not mention side effects, requirements (e.g., internet access for URL), limitations (e.g., page bounds), or return behavior. This is insufficient for a tool that likely performs file downloads and processing.

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 concise sentence that front-loads the core purpose. There is no redundancy or wasted words, making it easy for an agent to quickly understand the tool's basic function.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is far too sparse. It does not explain return format, error conditions, or how page ranges are validated. This is a minimal viable description at best; for a tool of this complexity, more context is needed.

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 67%, with descriptions for url and end_page but not start_page. The description's phrase 'page range' adds context connecting start_page and end_page, but it doesn't explain the default behavior of start_page (covered by schema default) or the meaning of 'inclusive' beyond the schema. It partially compensates but adds limited value.

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 'Extract PDF page range text' clearly specifies the action (extract text) and the resource (PDF page range), distinguishing it from generic PDF extraction tools like extract_pdf. However, it doesn't explicitly differentiate from siblings such as pdf_metadata or ocr_url, leaving some ambiguity about the exact output format.

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 alternatives like extract_pdf or pdf_metadata. It does not mention prerequisites, use cases, or exclusions, leaving the agent without context for choosing this tool.

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