export_resume

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

With no annotations, the description fully discloses output format traits: ATS-safe, single-column, real text. It also describes the return object shape. It does not mention file overwrite behavior or error conditions, but covers key behavioral attributes.

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?

Four sentences with no wasted words. Purpose, content guidelines, format and layout, and return type are each clearly stated in a logical order.

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?

The description covers input formats, output format, layout properties, and return structure. Missing details on filename behavior or error handling are minor given the output schema exists. Complete for standard use cases.

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?

Despite 0% schema description coverage, the description explains the content parameter (markdown vs structured JSON with syntax hints) and format parameter (pdf/docx). The filename parameter is not described, but overall adds significant value 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 clearly states it renders CV content to PDF/DOCX, specifying both input formats and output options. It differentiates from sibling tools like load_master_resume and save_master_resume by focusing on final export.

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 implies usage after resume completion ('Render finished CV content') and gives detailed formatting instructions. However, it does not explicitly contrast with siblings or specify when not to use the tool.

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