Create a tailored PDF CV with AI using your profile and job description.
Generate a CV/resume as PDF using AI based on the user's profile.
| Name | Required | Description | Default |
|---|---|---|---|
| template | No | CV template to use | |
| job_title | No | Target job title to tailor the CV for | |
| job_description | No | Job description to tailor the CV for |
Changes observed during successful MCP inspections.
v3.2.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the output format (PDF) and the input source (user profile), but says nothing about whether the generated file is stored or returned, whether profile data must exist first, or any permissions required.
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?
A single efficient sentence with no filler and the core action front-loaded. It is arguably under-specified for a tool with three tailoring parameters, but there is no wasted language.
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 no output schema, no annotations, and three optional parameters, the description should explain what is returned (a file, a URL, a document record) and how it relates to generate_and_store_cv. Neither is addressed, leaving key gaps for an agent.
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 template, job_title, and job_description are already documented. The description adds no syntax or behavioral detail about how tailoring works, so the 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 and resource ('Generate a CV/resume as PDF using AI') with the input basis ('based on the user's profile'). However, it fails to distinguish itself from the sibling generate_and_store_cv, leaving the agent unsure which to pick.
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?
No when-to-use guidance, no prerequisites, and no mention of the near-identical sibling generate_and_store_cv. The agent must infer from the name alone that this one does not persist the result.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.