React to a LinkedIn post

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the actor-identity nuance but does not go deeper into behavior like idempotence consequences, permission requirements, or what happens if the reaction already exists. No contradiction with annotations.

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 filler. It communicates the core action, the reaction types, and the actor scope efficiently.

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 operation with one required parameter and safety-relevant annotations already present, the description plus schema is sufficient for an agent to select and invoke the tool. It does not describe the return value or error conditions, but that is not essential for this kind of action without an output schema.

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 documents the reaction enum and organization_id meaning, covering 67% of parameters. The description reinforces the reaction categories and organization mode, but it does not add much semantic detail for post_urn beyond the schema's pattern constraint.

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 uses a specific verb ('Adds a reaction') with a clear target ('to a post') and actor scope ('as yourself or an organization'). This cleanly distinguishes it from sibling tools like linkedin_create_post, linkedin_delete_post, and linkedin_comment_on_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 intended use is immediately clear: react to a LinkedIn post. The description also clarifies that the reaction can be performed as the user or an organization, which helps disambiguate the optional organization_id usage. It does not explicitly name alternative tools, but no sibling overlaps with reacting to a post.

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