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

With only readOnlyHint=true in annotations, the description carries the behavioral burden and does so richly: it enumerates returned fields (name, headline, profile_url, followers or null when unknown), notes replies are nested under each comment, and explains the truncated/comment_count semantics. It even discloses that comments render as a sortable table in chat, which is non-obvious behavior.

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?

Front-loaded with the resource and its scope, then usage, then input handling, then output/summary behavior — a sensible order. It runs long and blends agent response-formatting guidance (themes, sentiment, disagreement) into the tool description, which costs a point on tightness.

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?

No output schema exists, so the description must describe returns — and it does, covering comment fields, nested replies, and the truncation signal. Nothing needed to call it correctly or interpret its results 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 coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema: 'Pass the link exactly as given; feed/update links, share links and bare activity ids all work,' clarifying accepted input formats and that no normalization is needed.

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 and resource (fetch every comment on one LinkedIn post) and immediately scopes it: 'Works for any public post, not only the user's own,' which separates it from get_my_linkedin_posts and search_linkedin_posts. An agent can pick this tool 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 concrete trigger conditions ('when they paste a LinkedIn post link and ask what people are saying, for a summary of the comments, or who commented'), which is clear usage context. It stops short of naming an explicit alternative or a when-not-to-use condition, so it lands just under the top band.

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