Optimize resume for a job

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

With no annotations provided, the description fully carries the burden. It discloses the core behavioral guarantee (uses only genuinely present information, never invents), the output format (PDF + DOCX), and the return values (ATS scores, changes, unverified requirements). It does not mention whether the tool mutates the application tracking state, but this is likely handled by sibling tools; overall, the description covers the most critical behaviors.

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 four sentences, front-loaded with the primary purpose, then flows through actions, constraints, and outputs. Every sentence adds value, with no redundant phrasing. It is concise yet comprehensive, a model of efficient writing.

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?

For a tool with only two parameters and no output schema, the description covers everything an agent needs: what it does, prerequisites (tracked application, master resume), output format, and return data. It even specifies constraints on information sourcing. The lack of an output schema is mitigated by explicitly listing the returned artifacts. This is complete for the tool's complexity.

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?

Both parameters are fully described in the schema (application and targetScore) with clear descriptions. The tool description adds context that ties targetScore to ATS scoring but does not provide additional syntax or usage details beyond what the schema already states. With 100% schema coverage, the description meets the baseline but adds no extra parameter-level semantics.

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 opens with a specific verb-resource pair: 'Generate a job-specific tailored resume for a tracked application.' It then lists concrete actions (surfaces keywords, reorders skills/bullets, adds summary) and explicitly states what it does NOT do (never invents information). This clearly distinguishes it from generic resume tools and even from sibling tools like generate_application_profile, which likely focus on other outputs.

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: it requires a 'tracked application' and uses information from the master resume/profile, implying that analyze_job and upload_master_resume must have been run first. However, it does not name any alternative tools or state when not to use it, leaving some ambiguity about its relationship to generate_application_profile or prepare_application.

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