support_set_reaction

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is structured data rather than description content. The description adds no behavior beyond restating the route: it does not explain what destructiveHint=true means here (e.g. whether removing a reaction is irreversible), whether set-to-"none" differs from setting like/dislike, or whether the call is scoped to the calling user. For a mutating, nominally destructive endpoint this leaves real gaps.

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 lines, zero filler, with the operation stated before the route. Nothing is redundant, though the terse form leaves the reader with no structure for edge cases.

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?

No output schema exists, so the description could reasonably say what a successful response returns or what happens to the previous reaction. Combined with an unexplained destructiveHint on what is nominally a reaction toggle, the definition is serviceable for calling the endpoint but incomplete for predicting its effects.

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 0% with three required parameters including a nested object, so the description must compensate. It partially does: the route template makes clear that `id` is the ticket id and `messageId` is the message id, which the bare schema would not convey. However, it says nothing about the `body.reaction` enum (like/dislike/none) already defined in the schema, nor whether "none" clears an existing reaction.

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 gives a specific verb+resource ("Set reaction to support message") and reinforces it with the concrete route PATCH /support/tickets/{id}/messages/{messageId}/reaction, which distinguishes it from siblings like support_send_message or support_get_messages. It stops short of naming what it is not, but the operation 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 / when-not-to-use guidance and no mention of alternatives. An agent must infer from the name alone that this tool applies to an already-existing message rather than composing or editing one.

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