Reaction

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

Annotations already declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the safety profile is covered. The description adds that reactions are anchored to a time position and require discovered ids, but says nothing about auth requirements, whether a second reaction at the same position replaces the first, 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?

Two sentences, zero filler, with the core action front-loaded and the id-discovery pointer immediately after. Every clause carries information the agent needs.

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 four-required-parameter write tool with no output schema, the description covers what it does and where the constrained id value comes from, which is the main gap in the schema. Missing only auth expectations and duplicate/replacement behavior, which are secondary for this operation.

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 75%, and the single undocumented parameter is 'reaction' (integer, no enum). The description compensates by directing the agent to get_track_part part=reactions for valid ids, which is the key missing semantic. It does not restate position units, but the schema already covers that.

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 uses a specific verb and resource ('Posts an emoji reaction') and scopes it to a position on a track, which cleanly separates it from siblings like toggle_like or post_comment. It stops short of explicitly naming those siblings, but the action 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?

It gives one concrete prerequisite — valid reaction ids come from get_track_part part=reactions — which is genuinely useful routing. However, it offers no guidance on when to use this versus related engagement tools (toggle_like, post_comment) or any preconditions such as authentication or track ownership.

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