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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only 'high-fidelity' and 'template engine,' which describe output quality and mechanism, not deeper behavioral traits such as file handling or overwrite semantics; it does not contradict any annotation.

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?

One sentence front-loads the action and output, then adds the key input and mechanism without redundancy or filler. Every phrase 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?

With detailed parameter descriptions, defaults, annotations, and an output schema, the definition supplies everything an agent needs to call the tool correctly. The description itself is short but combines with structured metadata to cover the tool's purpose, inputs, and safety profile.

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%, and each parameter has a meaningful description with defaults and examples for color, filename, and template. The description's mention of 'structured resume data' and 'template engine' lightly echoes resume_data and template but adds no semantic information beyond the schema.

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 action pair — 'Render and generate a high-fidelity PDF' — with an explicit input source ('structured resume data') and engine. It is clearly distinct from sibling tools such as civify_parse_cv, civify_tailor_cv, and civify_score_ats, none of which produce a PDF.

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 'from structured resume data' makes the precondition clear: this tool should be called when fully structured resume JSON is available and a rendered PDF is needed. It does not name alternative tools or state when not to use it, but no sibling tool offers the same PDF-generation capability.

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