load_cv

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

With no annotations, the description explains the key behavior: the photo is removed from the returned text and reattached later. It implies a safe read operation without side effects, though it does not explicitly state non-destructiveness.

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?

Three concise sentences plus a one-line Args section. Every sentence adds value: purpose, rationale, usage guidance, and parameter definition. No wasted words.

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 an output schema available, the description does not need to detail return format. It adequately explains the transformation (photo removal) and usage context. Could mention that the output is YAML text, but the title implies it.

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 single parameter cv_path has a minimal description ('path to the CV YAML') that adds little beyond the property name. Given 0% schema description coverage, more detail would be beneficial, though the default value is noted in 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 returns the CV YAML with the photo removed, a specific verb-resource pair. It distinguishes from siblings (fetch_offer, generate_pdf) by focusing on loading CV data only.

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?

Explicitly tells when to use this tool (instead of opening the file directly) and why (photo is huge and useless). Also notes that the photo is reattached by generate_pdf, providing context for downstream usage.

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