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

The description implies a non-destructive operation by stating extraction and returning a new PDF, consistent with the destructiveHint=false annotation. However, it does not disclose additional behaviors such as failure modes, URL constraints, or the relationship between async and synchronous modes beyond what the schema provides.

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, precise sentence (14 words) that states the core functionality immediately. Every word is essential, and the structure is front-loaded with the verb and resource.

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?

Without an output schema, the description explains the return as 'a new PDF', which is sufficient. The 4 parameters are fully documented in the schema. The description adequately covers the tool's purpose and result, though it omits nuances like the job ID return for async calls (covered in schema). Overall, it is complete enough for a tool with good schema coverage.

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 covers all 4 parameters with descriptions. The tool description does not add any extra meaning beyond the schema, meeting the baseline of 3. No additional parameter context is provided.

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 clearly states the action ('Extract a subset of pages'), the resource ('from a PDF'), and the output ('return the result as a new PDF'). It distinguishes from sibling tools like delete-pdf-pages and split-pdf-file by specifying extraction of a subset.

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, nor does it state prerequisites or conditions. It only states the basic function without context for selection.

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