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

The description clearly states the write operation (add or remove reaction), explains how to toggle the behavior, and discloses a side effect (marking the conversation as read). Annotations already flag idempotency, so the description adds meaningful behavioral detail without contradiction.

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 purpose is stated first and the supporting parameter guidance is brief and organized. It is not trimmed to one sentence but every clause adds practical value.

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 single-action mutation tool, it covers inputs, source of the key ID, and side effects. Missing explicit error/rate-limit info is not critical given annotations and 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?

Parameter descriptions in the schema are already detailed, and the tool description adds useful guidance on where message_urn comes from and how to remove a reaction. This goes slightly beyond the baseline for fully-schema-documented parameters.

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 and resource: 'Add or remove an emoji reaction on a LinkedIn message.' This clearly identifies the tool's function and distinguishes it from sibling conversation tools like archive_conversation or list_conversation_messages.

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 gives practical guidance by telling the agent that message_urn comes from list_conversation_messages and that setting react to false removes the reaction. It also notes the read side-effect when conversation_linkedin_id is passedhols, giving clear usage context without explicit exclusion of alternatives.

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