generate_pdf

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

No annotations exist, so the description bears full responsibility. It discloses the external dependency (notboringresume.cloud), the output behavior (writes to output_path, returns {path, overflows}), the overflow handling pattern, and the photo reattachment logic. However, it does not mention authentication requirements or error behavior if the external service fails.

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 well-structured: a one-line purpose, output note, overflow guidance, then a clear 'Args:' list. Every sentence adds value; no redundancy. It is appropriately sized and front-loaded.

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?

Given the tool has no output schema and no annotations, the description provides adequate context: explains the transformation, the parameters, the external service dependency, and the overflow retry logic. It does not require additional detail for typical 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?

Schema description coverage is 0%, yet the description fully explains all three parameters via an 'Args:' section. It provides purpose, defaults, and usage context for each (e.g., yaml′s role in tailoring, cv_path′s photo reattachment, output_path′s default). This fully compensates for the schema gap.

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 first sentence clearly states the action: 'Render a YAML CV into a one-page PDF via notboringresume.cloud.' This specifies the verb (render), resource (YAML CV), and output (one-page PDF). It distinguishes from siblings like load_cv (which loads CV data) and generate_letter_pdf (letter 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 description provides internal usage tips (e.g., handle overflow by shortening YAML and retrying, omit yaml for a quick test) but does not explicitly differentiate from sibling generate_letter_pdf or state when to use this tool over others. The guidance is partially present but lacks cross-tool context.

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