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

With no annotations, the description carries the full burden and does well: it discloses pagination (100/page), credit cost (7, cached or not), and a refund on failure. The member-id/vanity_name caveat explains a non-obvious result shape. It omits auth requirements and rate limits, but the cost and refund disclosures are strong.

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 core action and return fields, then constraint, then cost. Dense but nearly every sentence earns its place; the member-id sentence is the one most likely to be skimmable, but it conveys non-obvious behavior.

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 (name, headline, link, reaction type), plus pagination and cost. It covers what an agent needs to call and interpret the tool, though field-level result details remain partly inferred.

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% (baseline 3), and the description adds meaning beyond the schema by stating the url/comment_url mutual exclusivity and the actor.url member-id behavior. That interpretive context elevates it above the schema-only baseline.

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 who reacted to one post') with the exact payload returned (name, headline, link, reaction type). This is easily distinguishable from get_linkedin_post_comments and get_linkedin_post without opening a 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 an explicit selection rule: 'Give exactly one of `url` or `comment_url`', and describes the two modes (post reactions vs one comment's reactions). It also routes to a sibling ('linkedin/profile takes it'). It does not name an alternative reactions tool or state exclusions, so it falls just short of the top tier.

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