cv_export_pdf

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the output format and that a path is returned, but does not explain side effects such as where the file is written, whether existing files are overwritten, permissions, or failure behavior.

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 short sentences with no wasted wording. The purpose and return value are front-loaded, followed by concise parameter guidance.

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?

For a simple one-parameter tool with no output schema, the description covers the core action, return value, template sourcing, and default behavior. It leaves out file-system side effects and overwrite semantics, but the essentials are present.

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 schema provides 0% description coverage for the single 'template' parameter. The description compensates well by saying template ids can be found via profile_get preferences or the web app, and that the default is the user's chosen template.

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 gives a specific verb and resource: render the general (untailored) CV to an A4 PDF and return its path. The parenthetical 'untailored' explicitly contrasts this with a tailored CV, which helps distinguish it from sibling pack-related tools.

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?

It implies the tool is for exporting the general CV, but does not state when to use it instead of alternatives such as a tailored pack export. The only explicit guidance is about where to find template ids, which is parameter-oriented rather than usage-oriented.

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