pdf_auto_crop_page

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

No annotations are supplied, so the description must carry the full behavioral burden. It explains the cropping approach but does not disclose whether the file is modified in place, what happens to the original, or how page_number=None affects the crop (e.g., all pages vs first page). This is a significant gap for a mutating operation.

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, clear, front-loaded sentence with no filler. Every word contributes to the core purpose.

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?

Although an output schema exists, the description still lacks critical context: how page_number and padding behave, whether the operation is destructive, and what the return value signifies. The tool is simple enough, but ambiguity around default behavior and parameters makes it incomplete.

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?

With 0% schema description coverage, the description must explain the parameters. It only mentions 'page' generically, but fails to explain the required pdf_path, the meaning of padding, or the semantics of page_number being null. The schema provides no descriptions, so the agent is left guessing.

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 uses a specific verb ('crop') and resource ('PDF page'), and clearly states it auto-detects content boundaries to remove blank margins. This distinguishes it from the sibling manual pdf_crop_page tool.

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 automatic cropping but provides no explicit guidance on when to choose this over pdf_crop_page or other PDF manipulation tools. No exclusions or alternative selection advice is given.

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