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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds workflow context and post_id provenance, but does not disclose pagination behavior or whether replies are excluded. No contradiction with annotations exists.

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 two short sentences with no filler. The main operation is front-loaded, followed by a prerequisite and a usage context. Every clause earns its place.

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 simple read-only list operation, the description plus schema is mostly sufficient, but it does not clarify whether only top-level comments are returned versus replies, and it does not describe pagination/offset behavior. With no output schema, an agent would benefit from additional boundary or return-shape context.

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?

The schema already provides detailed descriptions for post_id and account_id, and the tool description mostly restates post_id provenance already present in the schema. It adds no meaning for offset or account_id, and offset has no schema description. With 67% schema coverage, the description does not compensate for the undocumented parameter.

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 a specific operation and resource: 'List comments on a LinkedIn post.' It also identifies the required input source for post_id. It does not explicitly contrast with sibling tools like linkedin_list_comment_replies, but the resource scope is unambiguous enough for an agent.

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 a concrete prerequisite ('Requires post_id from search/list/get post') and a practical workflow cue ('Use before deciding which comments need a reply'). It does not name alternatives or give when-not-to-use conditions, but the context is clear and actionable.

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