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

Annotations declare non-destructive, idempotent, open-world behavior, and the description adds substantial context beyond that: quota budgets per tier, exemption rules, that failed attempts still consume budget, and the LINKEDIN_DAILY_LIMIT_REACHED signal with retryAt semantics. This is a genuinely useful disclosure for a rate-limited mutation tool, though it says nothing about auth requirements or what a successful response contains.

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 purpose is correctly front-loaded in the first sentence, but the remaining text is a dense block of quota tiers, exemptions, and reset timing that reads more like internal policy documentation than a tool description. Every sentence is arguably operationally relevant, but the budget enumeration is heavy and could be compressed without losing agent-relevant meaning.

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 carry return/error behavior, and it does cover the key failure mode and the authoritative-backend principle. For a 3-parameter, fully-schema-documented tool with annotations covering the safety profile, the description is complete enough, missing only success-response and auth detail.

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%, including a detailed postedId URN format guide and an enumerated reactionType, so the schema carries the full parameter burden. The description adds no parameter detail beyond that, so the baseline 3 applies.

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 ('React to a LinkedIn post') and names the reaction vocabulary via the parenthetical. It is clearly distinguishable from siblings like linkedin_create_comment and linkedin_create_reshare by the resource-action pairing, though it never explicitly contrasts with them.

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 gives strong operational guidance about retry behavior and quota exhaustion ('do not self-throttle', 'never loop immediately'), which is real when-to-act guidance. However, it offers no guidance on choosing this tool over sibling alternatives such as linkedin_create_comment or linkedin_delete_reaction, so tool-selection guidance is only implied.

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