pdf_split

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

The description adds a key behavioral trait by disclosing that the PDF is sent to the renamed.to API for processing, which is useful context. However, with no annotations, it does not disclose whether the operation is read-only, modifies the original file, is asynchronous, or has any rate limits or side effects. The external API mention is a positive but insufficient disclosure.

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 two sentences, front-loaded with the core purpose and strategy options. The second sentence adds essential external API context. Every word earns its place; there is no redundancy or filler.

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 tool that sends PDFs to an external API and has no output schema, the description is somewhat incomplete. It does not mention whether the operation returns anything, how to monitor progress (potentially via sibling 'status'), or whether the original file is modified. This would be clearer with a note on asynchronous behavior or output handling.

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%, and all parameters have descriptions (e.g., strategy enum values). The description's mention of 'content or topic using AI, bookmarks, or page ranges' aligns with the enum values but does not add any new semantics beyond what the schema already provides. Baseline of 3 applies.

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 tool's function: 'Split PDFs by content or topic using AI, by bookmarks, or by page ranges.' It uses a specific verb (split), a specific resource (PDFs), and lists the main modes. This clearly distinguishes it from sibling tools like rename, watch, and status.

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 usage by listing splitting strategies (content/topic, bookmarks, page ranges), but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. It lacks context such as prerequisites, typical use cases, or when not to use it.

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