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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: comment-mode reactions require a connected LinkedIn account, and it enumerates the reaction types returned. It doesn't mention rate limits or cursor exhaustion behavior, but that is a minor gap.

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?

Front-loaded with the core purpose, then parameter sourcing, then return shape. Four sentences with little waste; the parenthetical sourcing notes are dense but informational rather than padding.

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 explaining returns and does so by naming reactor profiles and the reaction-type set. Combined with the schema's cursor pagination documentation, an agent has enough to call this correctly; only edge-case behavior (e.g. empty results, pagination termination) is unaddressed.

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% and the schema already documents provenance for each parameter (cursor, postUrl preferred-unless, commentId optionality, activityUrn preference). The description largely restates this, adding only the note that commentId works for your own comments. 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 and resource ('Get reactions on a LinkedIn post or on a specific comment') and immediately distinguishes the two modes of operation. An agent can tell this apart from linkedin_get_post_comments or linkedin_react_to_post without opening any other 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?

Explicitly routes the agent: supply activityUrn from linkedin_get_person_posts or a post URL, and pass commentId only when comment reactions are wanted, sourced from linkedin_get_post_comments or linkedin_get_nested_comments. It does not say when to prefer this over linkedin_get_my_engagement or how it relates to linkedin_get_post_analytics, so it stops short of full when/when-not coverage.

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