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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, but the description still adds real context: the action is performed publicly as the Page and is limited to Facebook by platform policy. It stops short of saying whether the like is attributable/visible on the Page feed or whether permissions are needed.

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?

A single dense sentence with the platform tag front-loaded and no filler. The parenthetical about Instagram/YouTube is justified by preventing wasted calls, though the abbreviations ('fb only', 'fb_post_id') make it slightly clipped.

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 mutation tool with no output schema, the description covers platform scope and identifier choice but omits the essentials an agent needs, notably that a comment_id must be supplied and which Page context the action runs under. No error or permission behavior is described.

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?

With 0% schema description coverage the description must carry parameter meaning, and it does: it defines the polarity of `like` and explains that `post_id` is the FB post id with `post_uuid` as an alternative identifier. `comment_id` is left unexplained, and it is not stated that comment_id is effectively required despite the 0-required-parameter 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?

States a specific verb pair (like / unlike via like=false) and the resource (a comment), plus the acting identity ('as the Facebook Page') and the platform scope (Facebook only). An agent can distinguish this from reply_comment or hide_comment without consulting the schema.

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?

Explicitly gives the toggle condition (like=false to unlike) and rules out Instagram/YouTube because no API exists, which is a genuine when-not statement. It does not, however, say when to prefer this over sibling comment actions such as reply_comment or hide_comment.

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