tailor_resume

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

With no annotations, the description carries the full burden. It discloses that the operation clones (implying a non-destructive copy) and uses AI for tailoring. However, it does not mention side effects like creating a new resume resource, whether the original is modified, or the asynchronous nature of AI processing. This is a moderate disclosure typical for a tool without annotations.

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 a single, front-loaded sentence with no unnecessary words. It efficiently communicates the core action and object, earning a perfect score for conciseness.

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?

Without an output schema, the description should clarify the result of the operation (e.g., a new resume ID or the tailored resume content). It implies cloning but does not explicitly state the return value or whether the original is untouched. This gap makes it adequate but not fully complete.

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 coverage is 100%, so parameters are well-documented. The description adds context by linking resumeId and jobDescription, but does not provide additional syntax or format details beyond what the schema already states. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('Clone a resume and use AI to tailor it') and the target resource (resume for a specific job description). It distinguishes from siblings like clone_resume (which only clones) and enhance_text (which enhances generic text) by specifying the tailoring purpose.

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 when you need to tailor a resume for a specific job posting. It does not explicitly mention alternatives or exclusions, but the purpose is self-evident given the sibling tools. A brief note on when to use clone_resume instead would have made it perfect.

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