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

The description goes well beyond annotations by warning about daily post_like budgets, business hours gates, and the fact that bypassing 'disables ALL LinkedIn safety limits.' It explicitly discloses the risk of account restriction or flagging, which is essential for an agent to make a risk-aware decision.

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 description is front-loaded with the core purpose, then logically moves to target resolution, account selection, and finally a prominent risk warning. Every sentence carries useful information, and the warning is appropriately emphasized.

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?

The main gap is a structural inconsistency: the input schema declares zero properties while the description names several required/optional inputs. This could confuse an agent about how to invoke the tool. The return value/output is not mentioned, but the absence of an output schema reduces that concern.

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?

Even though the input schema has zero parameters, the description explains the key inputs in prose: platform, profileUrl, leadId, and accountId, plus the bypass behavior. It earns the baseline 4 for zero-param schemas but loses a point because exact parameter names and the bypass flag name are not formally specified, and the prose conflicts with the empty schema.

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 opens with a specific verb and resource: 'Like a lead's most recent post to warm the relationship through engagement.' It clearly distinguishes this from sibling tools like comment_on_post or send_message by stating the interaction type and intent.

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?

It provides strong context on when to use the tool and how to select the correct target/account, including the current platform constraint and a pointer to campaignstack_list_accounts for multi-account workspaces. It does not explicitly name alternative tools or state when not to use this tool, but the use case is clear enough.

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