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

Annotations already declare this a safe, idempotent, non-destructive read with no external side effects, so the safety profile is covered. The description adds one useful domain constraint (the 220-character limit) and the analysis dimensions, but says nothing about permissions, rate limits, or output shape beyond the enumerated checks.

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?

A single front-loaded sentence led by the verb+object, then a tight colon list of the four checks. Each clause adds scoping information rather than filler, though the sentence is dense enough that a separate usage line might have been clearer.

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 no output schema, the description carries the burden of saying what the tool reports, and it does so by listing the four diagnostic dimensions. For a read-only analysis tool with full schema coverage and rich annotations, this is nearly complete; only explicit sibling routing is missing.

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 all four parameters (headline, role, focus, skills) are already documented in the schema, and the description adds no syntax or format guidance for the optional role/focus/skills inputs. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb and resource (check a LinkedIn headline) and enumerates exactly what gets checked: length vs the 220-character limit, search-result truncation, job-title positioning, and buzzwords. It does not name its obvious sibling generate_linkedin_headline, so the check-vs-generate distinction rests on the verb alone.

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?

Usage is implied by the diagnostic nature of the output list and the phrase 'buzzwords or vague claims to replace', which suggests evaluating an existing headline. There is no explicit when-to-use, when-not, or pointer to generate_linkedin_headline for starting from scratch, leaving the routing to inference.

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