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

Annotations already declare the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=true). The description restates the react=false removal and the mark-as-read side effect, but the same mark-as-read behavior is already in the conversation_linkedin_id schema description, so the description adds little beyond structured fields. No quota/rate-limit context despite the account quota siblings.

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?

Front-loaded with the verb+resource and mostly tight, but it repeats the message_urn provenance twice ('returned by list_conversation_messages' and again 'message_urn from list_conversation_messages'), which slightly bloats the sentence.

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?

Covers the mutation direction, the URN source, the side effect, and the sibling alternative; an output schema exists so return values need not be explained. Remaining gaps (permissions/scope requirements, quota behavior) are minor for a reaction toggle.

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 coverage is 100%, setting a baseline of 3, but the description adds a concrete message_urn format example (urn:li:msg_message:(urn:li:fsd_profile:…,123456789)) that the schema lacks, plus reinforces the emoji and react semantics. It provides modest value beyond the schema but not exhaustive per-parameter guidance.

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 (add/remove) and resource (emoji reaction on a LinkedIn message), and distinguishes the action from sibling tools: like_post/comment_post operate on posts, send_message on words. An agent can identify this as thread-message reaction handling without opening the schema.

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 explicit when-to-use ('an emoji reaction on one message inside a thread') and names the alternative and the condition that selects it ('to reply in words use send_message'). It also spells out how to undo the action (react=false).

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