laddro.coverLetters.generate

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

Annotations (readOnlyHint=false) indicate this is not read-only, and the description clarifies it generates and returns a PDF. It does not mention side effects like saving to the database, but for a generation tool that returns output directly, this is acceptable. 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?

The description is two sentences, each providing essential information: what the tool does and what it returns. No fluff or unnecessary details, making it easy for an agent to parse quickly.

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 the tool's complexity (8 params, output schema exists), the description is sufficient to understand its purpose and basic usage. It could be more explicit about how it differs from laddro.coverLetters.create, but overall it covers the key aspects.

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 100% description coverage for all 8 parameters, so the schema already explains each parameter's meaning. The description adds minimal value beyond mentioning that the tool uses 'resume and job description,' which is already implicit in the parameter descriptions.

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 action ('AI-generate a personalized cover letter'), the required inputs ('resume and job description'), and the output ('Returns a PDF'). This distinguishes it from sibling tools like laddro.coverLetters.create or laddro.coverLetters.get, which serve different purposes.

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 implies usage scenarios (when you have a resume and job description and need a PDF), but provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools. No alternatives are mentioned, leaving the agent to infer usage context.

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