pdf_delete_page

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

With no annotations, the description must disclose behavioral traits. It only says 'Delete a page from a PDF,' which adds nothing beyond the tool name. It does not mention whether the operation is irreversible, how the file is handled (in-place vs new file), or any permission requirements.

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 concise sentence, which is structurally acceptable. However, it is under-specified and essentially restates the tool name, providing little value beyond the title. It is not bloated, but it sacrifices necessary detail for brevity.

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 has two required parameters and an output schema, indicating a moderate complexity. The description is too minimal to guide correct usage, lacking critical details like page numbering convention, file path handling, or notable side effects. It leaves the agent to guess essential information.

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 0%, so the description must compensate. It does not explain that pdf_path is the file location or that page_number might be 0-indexed or 1-indexed. It merely uses the word 'page' which parallels the parameter name, providing no additional meaning.

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 (delete) and the resource (a page from a PDF), which distinguishes it from sibling tools like pdf_crop_page or pdf_rotate_page. However, it does not explicitly differentiate itself from alternatives or mention any edge cases, so it falls short of a 5.

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 mention prerequisites, constraints, or exclusions. It simply states the action with no context.

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