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

Beyond the annotations, it discloses idempotency ('liking an already liked comment succeeds and changes nothing'), a genuine side-effect caveat ('does not mark the comment as read or answered'), and explicit error semantics (403 reconnect_required / 401 reauth_required, relay to user rather than retry). This adds substantial context beyond readOnlyHint/idempotentHint.

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?

Core purpose is front-loaded in the first sentence, and each following clause carries actionable information (id form, idempotency, read-state caveat, error codes). It is dense and slightly long, but nearly every sentence earns its place; minor trimming possible on the reaction explanation.

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 two-parameter mutation tool with no output schema, the description covers identity, platform scope, id semantics, idempotency, read-state side effects, permission/error handling, and safe-usage constraints. Nothing an agent needs to invoke it correctly appears missing.

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%, so baseline is 3, but the description adds real disambiguation: message_id is the '#id shown by get_inbox_conversation and get_next_unanswered, not the conversation id.' That resolves a likely agent error the schema alone leaves ambiguous. The like/remove toggle is only covered by the schema, not elaborated.

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 names a specific verb (like / remove the like), the exact resource (a comment on one of the workspace's posts), the acting identity (the connected account), and the supported platforms (Facebook, LinkedIn Page, TikTok). This is clearly distinguishable from siblings like delete_inbox_comment, hide_inbox_comment, or reply_to_inbox.

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 explicitly states when to use it ('only comments the user asked you to like, or that match a rule'), when not to ('never like in bulk on your own'), and names alternatives for adjacent needs (mark_inbox_read or exclude to move past without replying). The Facebook reaction limitation ('no app can add Love') is a specific usage boundary.

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