set_msg_emoji_like

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the dual add/cancel operation via set_like, which is the key behavioral trait. However, it says nothing about permissions, rate limits, failure behavior for invalid or deleted message IDs, or what the call returns.

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 sentence is front-loaded and efficient, but the three :param lines duplicate the schema descriptions word-for-word, which is pure redundancy rather than added value.

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 annotations and no output schema, the description covers what it does and what each parameter means, but omits permissions, error semantics, and any note on whether reactions are idempotent or reversible. Adequate but with clear gaps.

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%, so all three parameters are already documented in the schema. The description reproduces those same parameter descriptions verbatim, adding no format details, valid ranges, or edge-case notes beyond what the schema provides.

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 and resource: add or remove an emoji reaction on a specified message, and flags itself as a NapCat extension interface. This is distinguishable from siblings like send_like (which targets users, not messages), though the description does not call out that distinction explicitly.

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?

There is no guidance on when to use this versus related tools (send_like, send_poke, set_essence_msg), nor any prerequisites such as needing a valid message_id from the same account. The only implied usage comes from the verb itself.

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