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 needs no restatement. The description adds one piece of behavioral context the annotations lack — that the tool is unimplemented — but says nothing about pagination behavior, what reaction data is returned, or failure modes when called.

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 short sentences with no filler; the core capability leads. The single most decisive fact for an agent — that the tool is unavailable — is placed last instead of first, which is a structural inefficiency.

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 list tool with a fully documented three-parameter schema and no output schema, the risk is low. However, the description is incomplete about the unavailability situation: it does not say whether calls error, return empty, or what alternative exists, which is what an agent most needs from a stub tool.

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%, so limit, post_id and in_workspace are all documented in the schema itself. The description adds no format or constraint detail beyond that (e.g., what a valid post/activity ID looks like), so 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?

States a concrete verb and resource (list reactions on a specific LinkedIn post) and enumerates reaction kinds, which separates it from siblings like linkedin_add_comment. It does not name a sibling or scope boundary, and the trailing 'Not available in this version' muddies whether the tool actually performs the described action.

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?

'Not available in this version' is a genuine usage signal — it tells the agent not to invoke the tool — but it is buried at the end of the description rather than front-loaded. There is no guidance on what the agent should do instead (e.g., linkedin_raw_request), so the agent is left without a fallback path.

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