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

Goes well beyond the annotations: it discloses the leaderboard point awarded to the author, that the target gets notified, that rapid liking returns a rate_limited error, and that the action is reversible in one call. Annotations only supply destructiveHint/idempotentHint flags; this text explains the actual side effects and failure mode. Minor tension with destructiveHint=true and 'runs without asking first', but not a contradiction since unliking does remove existing state.

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?

Front-loaded with the core action and reversal, which is good, but 'as the heart under it does' is UI flavor that costs a sentence without informing the agent, and the reversibility point is split across the last two sentences.

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, it covers the essentials an agent needs: both directions, the notification/points side effects, the rate-limit failure mode, and safe reversibility. Only a note on what the response returns or how to detect 'already liked' is 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%, and the description's clarification that post_id may be a comment_id only restates what the schema text already says. The 'liked false' semantics also mirror the schema description of the liked parameter, so almost no value is added.

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 (like) across two resource types (post OR comment) plus the reverse operation, so the full capability is visible in the first sentence. An agent can immediately tell this apart from siblings like vote_on_poll or follow_post without opening 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?

'Liked false takes the like back' and 'Runs without asking first: undone with one call' give clear operating context, including that no confirmation round-trip is needed. It stops short of naming alternatives (e.g. list_post_likes to check current state) or stating when not to use it.

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