optimize_resume

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

With no annotations, the description carries the transparency burden. It discloses the input (resume file path), processing (optimization for job position), and outputs (optimization description, structured JSON, generated .docx/.pdf paths). It does not explicitly state whether the original file is modified, but the mention of 'generated' files suggests non-destructive behavior.

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 is efficiently structured: a one-sentence purpose, a bulleted parameter list, and a one-sentence return summary. Every line adds value, and the structure makes it easy to scan. 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?

The description is complete for a tool with 4 parameters and an output schema: it covers purpose, all parameters, and return values. It could add explicit notes about side-effects (e.g., whether the input file is overwritten) or error conditions, but these are likely covered by the output schema and the tool's non-destructive design.

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 input schema has no parameter descriptions (0% coverage), so the description must compensate. It does so comprehensively: each of the 4 parameters is explained with types, defaults, and an example for job_position. This fully covers the semantic meaning beyond the schema's bare titles.

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 the tool's function: 'Optimize an existing resume based on target job position' (translated). The verb 'optimize' with the resource 'resume' is specific, and it distinguishes itself from the sibling tool 'generate_resume' by explicitly targeting existing resumes.

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 by noting the tool works on an existing resume (PDF/.docx/.doc) and includes parameter details for target position and optional requirements. However, it does not explicitly mention when not to use it or name the sibling tool 'generate_resume' as the alternative for creating new resumes, though this is strongly implied by the wording.

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