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

The description discloses idempotency ('reacting twice with the same emoji is a no-op'), which is a useful behavioral trait beyond the bare action. However, with no annotations, it does not mention permission requirements, side effects like replacing a previous reaction, or response format.

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 description is a single sentence that is front-loaded with the action verb and adds the idempotency note efficiently. Every word earns its place.

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?

Although the tool has two well-documented parameters and a concise description, it lacks any annotation or output schema, leaving the return behavior and exact side effects (e.g., whether a different emoji replaces an existing reaction) unspecified. The idempotency note helps but does not fully cover the context.

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?

Both parameters are fully documented in the schema with descriptions for 'emoji' (enum) and 'activityId' (UUID). The description adds no additional parameter semantics, so the 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 clearly states 'React to a post with an emoji,' which is a specific verb+resource action. Among the social siblings, this is the only tool for reactions, distinguishing it from posting, following, or connecting.

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?

The description provides no guidance on when to use this tool versus other social actions. No alternative tools or context conditions are mentioned.

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