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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description earns credit by disclosing the substantive analytical dimensions (character limit, SERP truncation, title placement, buzzword flagging), which is real behavioral context beyond the annotations, though it says nothing about the output/response shape.

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?

Two sentences, front-loaded with the usage trigger followed by the specific checks. Every clause carries information; no filler or repetition of the name/title.

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?

For a read-only analysis tool with no output schema, the description adequately conveys what the review covers, and the optional parameters are fully documented in the schema. It is nearly complete; only the shape of the returned review is left unspecified, which is a minor gap.

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. The description adds no syntax, format, or usage detail for these parameters, so the 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 description states a specific verb+resource ('Check a LinkedIn headline') and then enumerates exactly what it checks: 220-character length, search-result cut-off, leading job title, and buzzwords. This distinguishes it clearly from siblings like check_linkedin_about and generate_linkedin_headline without needing to open any 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?

It gives a clear usage trigger ('when the user wants their existing LinkedIn headline reviewed'), and the word 'existing' implicitly routes away from the generate_linkedin_headline sibling. However, it never names that alternative or states a when-not condition explicitly, so it stops short of a 5.

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