render_pdf

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

With no annotations, the description carries the full burden and delivers real behavioral context: the exact flags are chosen to avoid hangs and silently dropped output, and the tool verifies both exit code and actual PDF page count rather than trusting the process. The concurrency restriction (no batch loop on a shared Chrome profile) is a genuine side-effect warning, though permissions and failure/retry semantics remain unstated.

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?

Two sentences with no filler; the operation and its mechanism are front-loaded, and the constraint sentence follows immediately. Every clause earns its place.

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?

An output schema exists, so return values need no explanation. For a simple 2-parameter render tool, the description supplies the reliability and concurrency context an agent actually needs to call it correctly without over-explaining.

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 100%, so both parameters are already documented in the schema, including the pdf_path default. The description adds only the implicit reminder that html_path expects a single CV/cover-letter file, which is marginal value over structured data. Baseline 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?

States a specific verb (renders), a specific resource (one CV/cover-letter HTML file to PDF) and the mechanism (headless Chrome). No sibling tool overlaps this operation, so no disambiguation is required for an agent to select it.

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?

Gives explicit operational guidance: one call per file, never in a batch loop on the same Chrome profile. That is a clear when/how-not constraint, though it names no alternative tool for the batch case.

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