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

With no annotations, the description carries full responsibility for disclosing behavior. It only states 'extract', without mentioning whether the operation is non-destructive, what the output format is (e.g., base64 PDF), or any edge cases. The lack of behavioral detail is a significant gap for a tool that likely returns a new PDF.

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 with no wasted words. It is concise and easily parsed, effectively conveying the tool's core function without verbosity.

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 with only two well-documented parameters, but with no output schema and no annotations, the description should ideally note return values or behavior. It covers the purpose but lacks completeness regarding output format, which is a notable omission for an agent to correctly use the 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?

The input schema description coverage is 100%, with both 'pdf' and 'pages' clearly described. The tool description adds little beyond echoing 'specific pages', so the baseline of 3 is appropriate since the schema already provides the necessary parameter semantics.

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 specific pages from a PDF document' uses a specific verb ('extract') and resource ('specific pages from a PDF'), clearly distinguishing it from siblings like merge_pdfs, html_to_pdf, and pdf_info. The action and scope are unambiguous.

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 implies the tool is for extracting specific PDF pages, but it does not explicitly state when to prefer this over alternatives or mention any exclusions. There is no guidance on use cases or non-use cases, leaving room for ambiguity.

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