Extract PDF pages

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds genuinely behavioral nuance beyond them: page order is preserved "as written" and each page appears "each page once," which clarifies how duplicates/gaps are handled. It does not discuss permissions or large-file limits, keeping it at a solid 4.

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 lead with the core operation and constraint, followed by a one-line alternative pointer. No filler; the trailing web link is the only borderline element but is compact.

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?

With no output schema, the description usefully signals that the result is a single new PDF with the unselected pages excluded, and the output destination is covered by the schema's `output` param. It is complete enough to invoke correctly, though it doesn't state return shape explicitly.

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 100%, so the baseline is 3. The description adds meaning not fully captured in the schema by specifying "order as written, each page once," which disambiguates whether reordering or duplicate ranges are honored in the output.

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 and resource: "Make one new PDF from selected pages of a PDF," with the page-range syntax demonstrated inline. It also explicitly distinguishes itself from pdf_organize (the reorder/duplicate/delete sibling), so an agent can route correctly without opening a schema.

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?

Gives a clear when-to-use plus an explicit alternative: "To reorder, duplicate or delete pages use pdf_organize." It also scopes the operation ("The rest of the file is left out"). It stops short of naming pdf_split, the most confusable sibling for producing multiple files, so it is strong but not exhaustive routing.

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