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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'read-only... changes nothing' sentence largely restates structured data. However, the credit-cost model ('1 credit per result returned, minimum 1 per request') is genuinely new behavioral context an agent needs before choosing a large `count` value, which is real added value.

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?

Three short sentences: purpose first, safety second, cost third. Nothing is padded or repeated, and each sentence carries distinct information.

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?

With no output schema, the description must convey what comes back, and it only says 'returns public data' and 'members who reacted' without indicating the fields or whether reaction type is included. Cost and read-only behavior are covered, but the return shape and pagination limits remain unspecified.

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 100%, so activityUrn, count and start are already fully documented with formats and ranges, making 3 the baseline. The description adds only an indirect cost implication for `count`, with no mention of how `start` interacts with the credit charge or of a practical pagination ceiling.

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 ('List the members who reacted to a LinkedIn post'), which cleanly separates it from linkedin_get_activity_comments and linkedin_get_profile_reactions by resource type. It stops short of naming those siblings explicitly, so the differentiation relies on the tool name rather than the prose.

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 use case is inferable from the name and description, but there is no explicit statement of when to pick this over linkedin_get_profile_reactions or linkedin_get_post_detail, and no prerequisites such as needing a valid activity URN. Usage is implied rather than guided.

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