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

Annotations already signal a safe read-only, idempotent call. The description adds meaningful behavioral context: the call is strictly scoped to one exact comment, the IDs must be obtained via a resolution chain, and non-ID inputs are rejected. It does not cover pagination or response behavior, but the safety profile is already declared by 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 front-loaded with a clear one-line purpose and uses useful 'Post ID:' and 'Comment ID:' sections. However, those sections duplicate the schema descriptions nearly verbatim, and the inclusion of instagram_list_user_posts and instagram_list_post_comments as sources for a LinkedIn tool is confusing and likely erroneous.

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-parameter tool with no output schema, the description plus schema covers the essential invocation path: exact IDs, where to get them, what not to pass, and account disambiguation in the schema's account_id description. It lacks a description of return values and does not explain the optional offset parameter, which is a minor gap since the tool name and first sentence imply a list result.

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 75%, and the tool description mostly repeats the schema's own guidance for post_id and comment_id rather than adding new parameter-level information. The offset parameter is undocumented in both the schema and the description, and account_id guidance lives only in the schema. The chain clarifies the relationship between parameters but adds little beyond what the schema already provides.

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 opening sentence, 'List replies under one exact LinkedIn comment,' states a specific action and resource. It also distinguishes itself from sibling list tools like linkedin_list_post_comments by scoping the call to a single comment ID and showing the required chain: resolve post -> post.id -> list comments -> comment.id -> replies.

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 an explicit chain for obtaining required IDs and names the exact preceding tools (linkedin_search_posts, linkedin_list_post_comments). It also states hard exclusions: 'Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.' It does not, however, explicitly contrast this tool with alternatives like social_list_comment_reactions for deciding which operation to call.

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