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

Annotations already declare readOnly=false, destructive=true, idempotent=false and openWorld=true, so the safety profile is covered. The description adds only 'on behalf of the user' plus the intent gating; it never explains the non-idempotent behavior (re-reacting replaces the prior reaction) or what 'destructive' means for a reaction. Helpful but thin beyond structured fields.

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, front-loaded with the action and followed by the constraint. 'Use a supported LinkedIn reaction value' is slightly redundant since the schema already enumerates the values, but the phrasing is tight overall.

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 is the only place to say what a successful call yields, and it says nothing about the resulting state or how to undo a reaction. Against rich annotations and 100% schema coverage the omission is tolerable, but a mutation that changes visible state on a public post warrants more 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 description coverage is 100%, with post_id sourcing, the reaction enum, and account_id selection all documented in the schema. The description adds no syntax, format, or fallback meaning beyond it, so the 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 specific verb+resource ('Add a LinkedIn reaction to a post') and scope ('on behalf of the user'), and the LinkedIn qualifier distinguishes it from siblings like instagram_like_post and message_add_reaction. It stops short of naming a sibling alternative, so it doesn't fully earn 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?

Gives one real when-to-use condition ('only when the user's intent to react is clear'), which is genuinely useful gating guidance. However, it names no alternatives and offers no when-not guidance, e.g. no pointer to social_remove_post_reaction or linkedin_list_post_reactions, so usage remains implied rather than explicit.

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