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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the agent knows this is a safe, idempotent read operation. The description adds the reaction/people focus and engagement-analysis use case, but does not disclose pagination behavior via offset, whether authentication is required, or what the return shape looks like. With annotations covering the safety profile, a 3 is appropriate.

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 zero waste. The purpose is front-loaded in the first sentence, and the second sentence adds use-case context without padding. Every sentence 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 list tool with rich annotations and no output schema, the description is minimally adequate: it says what is listed and why. However, it does not explain the return format, pagination via offset, or potential rate limits, which are relevant when no output schema exists. The definition is functional but leaves clear gaps.

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 67%: post_id has a detailed description and account_id has a description, while offset is undocumented. The description adds no parameter-level meaning beyond what the schema already provides, but the schema carries the important ID semantics. Baseline 3 reflects that the schema does most of the work, though the unaddressed offset parameter and lack of description-level clarification keep this from being higher.

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 states a specific verb and resource: 'List people/reactions on a LinkedIn post.' An agent can immediately tell this is a read operation returning reaction data for a post. However, it does not differentiate itself from close siblings such as linkedin_list_post_comments or social_list_comment_reactions, so the agent must infer the distinction from the tool name.

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 offers a use case ('engagement analysis or to identify who reacted'), which gives clear context for when to call it. But it names no alternatives and provides no exclusions or conditions for choosing this over linkedin_list_post_comments or social_list_comment_reactions. Usage guidance is implied rather than explicit.

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