render_pdf_pages

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

The description explicitly discloses the side effect of clearing previously rendered pages first, which is important for an agent to understand the tool's full behavior. Since no annotations are present, the description carries the full burden and meets it well.

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 compact sentences, with the primary action first and the side-effect detail second. No unnecessary words or redundancy.

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?

With only one parameter and no output schema, the description covers the essential behavior, including the side effect of clearing old pages. There is no missing information needed for basic usage.

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 schema provides only the parameter name 'pdf_path' with type string and no description. The tool description mentions 'pdf_path' but adds only that it is rendered, not details about path format, file system context, or whether it is relative to a working directory. The name is self-explanatory but the description does not elaborate further.

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: 'Render every page of pdf_path to a PNG, one file per page.' It specifies the resource (pdf_path) and the exact output format, distinguishing it from unrelated sibling tools like list_directory or copy_file.

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 does not explicitly say when to use this tool versus alternatives, such as cleanup_rendered_pages. However, the note about clearing stale pages implies it is suitable for re-rendering after changes, but this is not stated as explicit guidance.

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