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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without the description. The description adds only a workflow hint, leaving return shape, pagination via offset, and result volume undisclosed.

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?

Two short sentences with the resource and prerequisite front-loaded and no filler. Efficient, though it could organize the workflow note more explicitly.

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 read-only list tool with strong annotations and no output schema, the description supplies purpose, prerequisite and intended use. The only meaningful gap is the undocumented offset/pagination behavior, which is minor here.

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 67%: post_id and account_id carry rich descriptions, while offset is undocumented in both places. The description echoes the post_id sourcing rule that the schema already states, so it adds little beyond the structured fields.

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+resource ('List comments on a LinkedIn post'), which is clearly distinct from write siblings like linkedin_comment_on_post and linkedin_reply_to_comment. It does not, however, explicitly distinguish itself from linkedin_list_comment_replies, so an agent must infer that this returns top-level comments rather than 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?

Gives a clear prerequisite ('Requires post_id from search/list/get post') and a workflow cue ('Use before deciding which comments need a reply'). It stops short of naming alternatives or exclusion conditions, but the context is unambiguous.

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