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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value on top: it clarifies no external side effects occur, describes the preview-then-confirm pattern, and points to the response envelope's nextAction. The confirm flag it references is not present in the schema (additionalProperties: false), which is a real inconsistency that costs a point.

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?

Four tight sentences with the core purpose, the negative scope, and the operational flow front-loaded. Every sentence carries information, though the trailing confirm instruction is the weakest given the parameter is absent from the schema.

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?

An output schema exists, so return-value detail is unnecessary, and the description still helpfully points to nextAction in the envelope. For a 12-parameter, multi-operation tool the description covers purpose, safety, and flow adequately, with only the phantom 'confirm' field left unresolved.

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 schema already documents all 12 parameters and the operation enum, setting the baseline at 3. The description names the four operations but adds no field-to-operation mapping beyond the schema's own 'Each operation accepts only its own fields,' and its mention of an undocumented 'confirm' parameter adds confusion rather than clarity.

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?

States a specific verb (draft) and concrete resources (career email, LinkedIn copy, resume bullets) and enumerates the four operations. No sibling tool drafts text, and the description makes that scope unambiguous without opening the schema.

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?

Explicitly states what it will not do ('does not save, send email or post externally') and prescribes a two-step confirm flow ('confirm: false for a preview... then repeat identical inputs with confirm: true'). It stops short of routing to a named alternative sibling, which keeps it from a 5.

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