save_tailored_resume

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

With no annotations, the description carries the full burden. It explicitly discloses the destructive behavior ('Replaces any previous version') and the LaTeX format, which are critical traits. It does not cover permissions or error handling, but for a simple save tool these are minor gaps.

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 sentences plus a concise Args list. Purpose and replacement behavior are front-loaded, and every parameter explanation is direct and useful with 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?

The tool is simple and the description covers purpose, key behavior, and all parameters. An output schema exists, so return values need not be detailed. The description is complete enough for an agent to select and invoke the tool correctly.

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?

Schema description coverage is 0%, so the description fully compensates by explaining all three parameters: job_id targets the job, content is the complete LaTeX document, and extension defaults to 'tex' with guidance. This adds essential meaning beyond the bare 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?

Description clearly states the tool stores a tailored resume as LaTeX and replaces any previous version for the job. The verb 'Store' with resource 'tailored resume for a job' is specific and distinguishes it from siblings like get_tailored_resume or tailor_resume.

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?

Provides clear context that this tool persists a tailored resume for a specific job and overwrites previous versions, which is a key usage consideration. It does not explicitly name alternatives or exclusions, but the context is sufficient for selecting this tool over related ones.

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