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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds the ID-resolution dependency chain, but discloses nothing about return shape, pagination behavior, or rate limits beyond what the schema's offset field implies.

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?

Purpose is front-loaded and the workflow is organized, but a large share of the text duplicates the schema's parameter descriptions verbatim, making it longer than it needs to be for the value added.

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 4-param read-only lister with no output schema, the description covers the critical prerequisite chain (resolve post_id -> list comments -> select comment_id) that an agent must follow. Return format is not explained, but nothing essential for a correct invocation is missing.

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 the baseline is 3. The prose largely restates the schema's own parameter descriptions (post_id and comment_id text is near-identical), adding no format or syntax detail beyond it.

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 (List) and resource (reactions on an exact comment), which distinguishes it from the write siblings social_react_to_comment and social_remove_comment_reaction, and from linkedin_list_post_reactions (post-level vs comment-level). An agent can tell what this does 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 sequencing: 'First resolve post_id, then list comments and select comment.id,' and names the resolver tools (linkedin_search_posts, linkedin_list_post_comments, etc.) that produce each ID. Clear context, though it never states a when-not-to-use case.

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