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

No annotations provided. The description mentions cost (1 credit/time) and automatic refund on failure, which are behavioral details. However, it does not disclose what happens to the original file, authentication requirements, rate limits, or error handling beyond refund.

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 extremely concise—a single sentence (two statements) that conveys the core function, cost, and refund policy. No unnecessary words. Perfectly front-loaded.

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 simple extraction tool with full schema coverage and no output schema, the description is adequate but incomplete. It lacks details about the default output filename behavior and whether the result is a new file ID. Minimal but functional.

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 100% (all parameters have descriptions). The description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 specified pages and save as new PDF) and the resource (PDF). It includes cost and refund policy, which adds clarity. However, it does not explicitly differentiate from sibling tools like pdf_extract_pages, though the name 'pdf_split' implies a distinct operation.

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?

No guidance on when to use this tool versus alternatives (e.g., pdf_extract_pages, pdf_organize). There is no mention of prerequisites, context, or scenarios where this tool is appropriate.

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