linkedin_react_to_post

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

Beyond the annotations (read-only false, destructive false, idempotent false), the description adds a valuable behavioral detail: calling on an already-liked post is a no-op rather than an error. This is contextual information the annotations do not capture, though it does not disclose all potential side effects.

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 two sentences, front-loaded with the core action, and every phrase earns its place: what it does, the reaction options, the default, and the no-op behavior. No wasted words.

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 simple two-parameter mutation tool with rich schema descriptions and reasonable annotations, the description covers the essential context: purpose, options, default, and an edge-case behavior. It lacks explicit return-value information, but no output schema exists and this is often unnecessary for write operations.

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?

The schema already fully describes both parameters, including accepted post formats and the reaction enum with default 'like'. The description repeats the default and reaction list but adds no meaning beyond the schema; the no-op behavior is about the operation, not parameter semantics.

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 opens with a specific action, 'React to a post', and clearly distinguishes the resource and scope. It enumerates the available reactions and notes the default, making the tool's purpose unmistakable and differentiating it from siblings like linkedin_comment_on_post or linkedin_save_post.

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?

The description provides clear context for when to use the tool: reacting to a post with a specified reaction type, defaulting to Like. It does not explicitly name alternatives or exclusions, but the action is straightforward and the no-op note clarifies a use case edge.

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