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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: 'Job Spotter never applies or sends anything' and 'Nothing sent is stored', which directly addresses side-effect and data-retention concerns an agent might have before invoking it.

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?

Front-loaded with the purpose, then trigger phrases, then the output inventory, then the safety caveats. It is dense but each sentence carries information; the long output enumeration sentence is the only slightly heavy part.

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?

With 10 optional parameters and no output schema, the description correctly compensates by describing the return contents in detail (proof lines, gaps, keywords, cover letter outline, common questions). The main residual gap is the absence of guidance on input combinations, though the schema descriptions largely cover the id-vs-job_text choice.

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 every parameter is already documented in the schema (cv, id, job_text, skills, titles, etc.). The description adds no parameter-level meaning beyond the schema, and its only passing reference ('keywords to use if true') is about output, not inputs. Baseline 3 applies.

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 title and first sentence state the resource ('everything needed to apply for a job') and the description enumerates the concrete deliverables (job requirements mapped to CV lines, gaps, keywords, cover letter outline, application questions). It is clear what the tool produces, but it does not explicitly differentiate itself from overlapping siblings such as match_cv or interview_prep, so it stops short of a 5.

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?

It gives concrete trigger phrasings ('help me apply for this', 'write my cover letter', 'what should I say in my application?'), which clearly signals when to reach for it. It supplies no exclusions or named alternatives, so the agent must infer the boundary with match_cv/interview_prep on its own.

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