export_cv_json

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

With no annotations provided, the description carries full burden. It discloses the core action (saving to local JSON) and the reloadable profile concept, but omits critical behavioral details: overwrite behavior, default output filename, return values, and error handling. This leaves significant unknowns for an agent invoking the 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 consists of two concise sentences, each earning its place: the first states the action, the second explains the purpose. No redundant or filler content.

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 nested cv object, optional filename, no output schema, and absence of annotations, the description is too sparse. It fails to explain the output_filename default, return behavior, or explicit compatibility with import_cv_json. An agent can infer the basic action but lacks enough context for correct invocation in all 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?

The description does not mention either parameter. 'Generated CV' loosely maps to the 'cv' parameter, but the optional 'output_filename' is entirely unexplained. With 0% schema description coverage, the agent receives no guidance on parameter usage, defaults, or optionality.

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 uses a specific verb ('Save') and resource ('a generated CV to a local JSON file'), clearly distinguishing it from siblings like generate_cv_pdf (PDF export) and import_cv_json (loading profiles). The phrase 'acts as a profile you can reload later' further reinforces its unique role.

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 clear context: use this tool to save a CV as a reusable profile, implicitly contrasting with PDF generation and importing. It does not explicitly name alternatives or state when not to use, but the 'profile you can reload later' signals the intended use case.

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