react_to_postAdd a reaction such as like, celebrate, or love to a LinkedIn post by providing its URL.
React to a LinkedIn post.
| Name | Required | Description | Default |
|---|---|---|---|
| post_url | Yes | Full URL of the post. | |
| reaction | Yes | Reaction type, e.g. "like", "celebrate", "love", "insightful", "funny", "support". "like" is the default. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v4.26.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare openWorldHint and destructiveHint, so some behavioral context exists. The description adds nothing beyond repeating the action, and notably does not explain why a reaction is flagged as destructive or what state changes it causes.
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?
The description is a single, front-loaded sentence with no wasted words. It is appropriately sized, though its brevity means it cannot carry much informational weight.
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 an output schema present and annotations covering safety traits, the description need not explain return values or risk. However, it omits any usage context relative to siblings and provides no behavioral nuance, leaving the definition minimally adequate for this simple action.
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 post_url and reaction thoroughly, including examples and a default. The description adds no parameter meaning beyond what the schema provides, which is the baseline expectation.
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 states a specific verb (react) and resource (LinkedIn post), making the core action clear. However, it does not differentiate from siblings like get_post_reactions or comment_on_post, so it stops short of a 5.
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?
No when-to-use, when-not-to-use, or alternative tool guidance is provided. The description only states the action, leaving selection context to be inferred from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.