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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, idempotent, closed-world), and the description adds real constraint context: outputs are capped at LinkedIn's 220-character limit and derived only from the supplied fields. It stops short of saying how many options are produced or in what format.

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?

Three short sentences with the resource and input constraints front-loaded and no filler. 'Does not change the profile' is slightly redundant with readOnlyHint=true, but it is cheap and reinforces the read-only nature.

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 should characterize the return value; it only guarantees the 220-character limit and is silent on option count, formatting, or variation strategy. For a multi-parameter generator tool, the behavioral picture is adequate but leaves a real 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 the schema already documents all seven parameters including the goal and tone enums, making 3 the baseline. The description names five of the seven inputs but adds no semantics beyond what the schema states, and omits goal and tone entirely.

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 resource (profile headline options) and the exact inputs they are built from, which separates it from generate_linkedin_hooks and format_linkedin_post. The verb is only implied by the tool name rather than the description text, so it falls short of a perfect score.

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 resource named (produce headline options from profile inputs) but there is no explicit when-to-use or when-to-prefer-a-sibling guidance. 'Does not change the profile' is a side-effect disclaimer, not a routing rule.

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