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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the behavioral requirement of resolving exact IDs before calling, and the 'Never pass' rules clarify input constraints beyond the 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 verbose and repetitive. The same 'Never pass' and 'Obtain with' instructions are duplicated in the description text and again inside the schema property descriptions for post_id and comment_id. It could be condensed significantly without losing information.

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?

The description covers the main complexity—how to obtain the required IDs—and includes guidance on the optional account_id. It does not describe the return format, but given the absence of an output schema and the fact that this is a read/list operation, the essential information for correct invocation is present.

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%, so all parameters are documented in the schema. The description adds extra semantics by explaining how to obtain post_id and comment_id via specific sibling tools and by explicitly listing what not to pass, which is not present in the schema.

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 clearly states the action 'List detailed reactions on an exact comment', specifying a verb, resource, and scope. It does not explicitly name sibling tools like linkedin_list_post_reactions, but the title and text make it unambiguous that this targets comment reactions, not post reactions.

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 explicit workflow instructions: 'First resolve post_id, then list comments and select comment.id', and also tells the agent what not to pass (e.g., 'Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it'). It does not compare against alternatives, but the usage context is clear.

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