generate_cv_pdf

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It states it saves a PDF, implying disk writes, but does not disclose potential overwrites, required permissions, error handling, or any destructive aspects. This is insufficient for a file-writing tool.

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, clear sentence with no wasted words. It is appropriately sized for the tool's purpose.

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?

Despite 100% schema coverage for parameters, the description is too brief for a tool with five parameters, nested objects, and environment variable defaults. It lacks an overview of the process, expected output, or behavioral details such as file naming conventions or confirmation of success. The lack of output schema further increases the need for descriptive completeness.

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 input schema has 100% description coverage for all five parameters, including nested objects. The description adds no additional meaning beyond the schema, which already explains defaults via environment variables. Baseline 3 is appropriate as the schema does the work.

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 tool generates and saves a CV as a PDF document. It distinguishes itself from siblings that output HTML, Markdown, or text, but does not differentiate from sibling tools like 'draft_cv_pdf' or 'generate_and_save_cv_pdf', which appear to have overlapping purposes.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it compares to similar sibling tools like 'draft_cv_pdf' or 'generate_and_save_cv_pdf'.

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