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

Annotations declare destructiveHint=true, which the description matches by describing a mutation ('Add'). It adds context: acts on behalf of the user, requires clear intent, and notes LinkedIn's rejection of plain 'like'/emoji. This goes beyond annotations without contradicting them.

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 concise sentences with no filler. The primary action is stated first, followed by a critical usage condition. Every word earns its place.

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?

The tool is simple and the schema covers all parameters thoroughly. The description adds the intent-clarity requirement and reaction validation note. No output schema exists, so return-value explanation is not required. Slight gap: no mention of authentication or account prerequisites, but these are implied by the platform context.

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 coverage is 100% with detailed descriptions for post_id, reaction, and account_id, including how to obtain IDs and avoid common mistakes. The tool description adds little beyond the schema, so a baseline 3 is appropriate.

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 ('Add'), a resource ('post'), and the on-behalf-of-user scope. The supported reaction values and the intent-clearance condition are explicit, clearly distinguishing it from sibling tools like linkedin_comment_on_post and linkedin_react_to_message.

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?

Provides a clear when-to-use condition: 'only when the user's intent to react is clear' and warns that plain 'like' or emoji is rejected. It doesn't explicitly name alternatives or when not to use, but the intent condition and reaction enum give practical guidance.

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