profile_set_master_cv

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

Since no annotations are provided, the description must carry the burden of behavioral context. It discloses specific technical constraints, dictating that the input must be 'Jinja2 HTML' and must utilize specific data variables ('personal, cv, languages'), which is critical behavioral information.

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 definition is perfectly concise, using two short clauses to establish the function and then the governing context ('Default template is used otherwise'). It front-loads the most important technical constraints.

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's simplicity (one required string input), the description is remarkably complete. It covers the technical format, the source data required for the format, and the context of its existence (overriding a default).

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?

With 0% schema description coverage and only one parameter ('html'), the description provides complete semantic context for that parameter. It defines exactly what the 'html' string must contain (Jinja2 format using personal/cv/languages data) rather than just requiring a string input.

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 explicitly states the tool sets a 'custom CV template,' identifying the precise action (set) and the target resource (CV template). It is highly specific and distinguishes itself by focusing on 'Jinja2 HTML' templates, which separates its function from general profile editing.

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 by noting that a 'Default template is used otherwise,' providing a clear contextual signal for when a change is needed. However, it provides no guidance on prerequisite states or explicit exclusion criteria compared to sibling tools like cv_export_pdf.

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