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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only' is redundant restatement rather than added disclosure. The one piece of genuine value is that the response contains both the emoji and its sender, which tells the agent the record shape. Pagination via cursor/limit is never acknowledged in the description.

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?

Two short sentences with the resource and result front-loaded; nothing is padded. The second sentence ('Read-only') is the only wasted clause since it duplicates an annotation.

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 five-parameter paginated list tool with no output schema, the description is minimally adequate: it says what comes back but not how paging terminates or what fields each reaction entry has. It leaves the agent to discover pagination behavior from the schema alone.

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 80%, so required fields and the limit/cursor pair are already documented in the schema. The description adds no meaning beyond it—no explanation of what a reaction page looks like or how cursor chaining works here. Baseline 3 applies.

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 the resource (emoji reactions on a message) and the payload (who sent each one), which is enough to separate it from siblings such as list_post_reactions or list_comment_reactions by subject type. It stops short of an explicit verb+scope statement, but the noun phrase is unambiguous.

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 when-to-use guidance, no stated prerequisites beyond the message context, and no routing to alternatives. An agent must infer from the name alone that this is for a single message that already exists and was located via a messaging list call.

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