laddro.resumes.tailor

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

Annotations indicate readOnlyHint=false, and description confirms it's a mutation ('rewrites content'). It adds that output is a PDF (or ZIP with cover letter), but does not disclose potential side effects, required authorization, or what happens if resumeId is omitted (though schema covers that). No contradictions with 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?

Description is two sentences, 20 words, and immediately conveys the core purpose. No unnecessary detail; every sentence earns its place. Front-loaded with the key action.

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?

Given 10 parameters and existence of output schema, the description covers the main output (PDF) and an alternative (ZIP with cover letter). However, it omits details about required vs optional parameters (positionName is required but description implies jobDescription/jobUrl needed) and does not address error scenarios or limits.

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 100%, so the description adds limited value beyond restating that jobDescription or jobUrl should be provided. It does not provide additional context like parameter relationships or format constraints.

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 tailors a resume for a job posting, mentioning key actions (rewrites content, returns PDF) and resource (resume). It differentiates from sibling tools like laddro.resumes.list and laddro.resumes.get by focusing on the tailoring action.

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?

Description provides basic usage guidance ('Provide either jobDescription or jobUrl') but fails to explicitly state when to use this tool over alternatives like laddro.resumes.export or laddro.resumes.render. No when-not-to-use or prerequisite conditions are mentioned.

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