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

Beyond the annotations, the description discloses the write semantics, the exact endpoint (POST /api/v2/chat/messages/{id}/reaction), and the constraint that the acting user must already exist. It does not mention idempotency, duplicate-reaction handling, or required permissions, but for an additive write with destructiveHint already declared, this is solid added context.

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 tightly packed sentence that front-loads the WRITE warning, then the action, then the precondition, then the endpoint. Every clause carries information; nothing is padding.

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 simple three-parameter write with no output schema, the description covers action, target, actor constraint, and transport endpoint. Only failure modes (duplicate reaction, invalid message id, permission errors) are unaddressed, which is a minor gap at this complexity.

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 all three parameters (id, reaction_type, user_id) are already documented in the schema with examples and constraints. The description restates examples and the existing-user rule rather than adding new semantics, so the baseline of 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 states a specific verb+resource: adding a reaction to a message, attributed to a user. That is clearly separable from stream_get_reactions (read) and stream_send_message (message post), although no sibling is named explicitly, so differentiation is implicit rather than stated.

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 supplies a precondition (user_id must be an existing user) and flags the call as a WRITE, which is useful for correct invocation. It never says when to prefer a different tool or when not to call it (e.g. reacting vs fetching reactions), leaving usage implied.

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