cleanup_rendered_pages

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

The description conveys the destructive nature ('Remove') but lacks details about permanence, recursive deletion, error handling, or side effects. With no annotations, the description carries the burden, offering only basic transparency.

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 with no filler. It efficiently conveys the core action and condition, achieving high clarity with minimal words.

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 is part of a PDF rendering workflow, but the description does not connect it to sibling tools like render_pdf_pages. It lacks information about the expected relationship between pdf_path and the folder, making it incomplete for effective use.

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?

The parameter pdf_path is required but the description does not explain its role. Since schema coverage is 0%, the description fails to compensate; users must infer that pdf_path identifies the PDF whose rendered folder should be removed, which is not explicit.

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 states the action clearly: 'Remove the rendered page-image folder'. It specifies the resource and a condition ('once it's no longer needed'), which distinguishes it from read/write/list tools. However, it doesn't explicitly explain how the pdf_path parameter maps to the folder, leaving minor ambiguity.

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 phrase 'once it's no longer needed' provides some guidance on when to use it, but it's vague and doesn't reference alternatives or concrete triggers (e.g., after render_pdf_pages). No explicit comparison with sibling tools is given.

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