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

Annotations already declare this a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds genuine context beyond that by disclosing the analysis dimensions the tool evaluates, which tells the agent what kind of feedback comes back, though it never states the response format or whether a score is returned.

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: the first front-loads the usage condition, the second enumerates the checks. Every clause carries content and nothing is padded, though the long comma-separated checklist is slightly dense.

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 must carry the burden of explaining what comes back; listing the check dimensions partially does this, but the agent still cannot tell whether the result is a pass/fail, a score, or rewritten text. It also omits how the optional role parameter changes the review, leaving the picture incomplete.

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 both parameters (about, role) are already documented in the schema, and the baseline is 3. The description adds the 2,600-character LinkedIn limit as useful context but never mentions the optional "role" parameter or how it shapes the check, so it does not exceed the schema.

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 names a specific verb and resource ("Check a LinkedIn About section") and enumerates the exact checks performed: the pre-"see more" preview on phone vs. computer, opening identity statement, quantified results, buzzwords, next step, and the 2,600-character limit. That is far more concrete than a generic "review" tool, though it never contrasts itself with near-neighbours like check_linkedin_headline or write_summary.

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?

"Use this when the user wants their LinkedIn About or summary section reviewed" gives a clear triggering condition tied to the user's intent. There is no when-not guidance and no named alternative (e.g., for drafting rather than checking an About section), so it stops short of the top band.

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