get_reaction

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

The description explicitly states 'GET /reactions/{id}', signaling a read-only, side-effect-free operation. However, with no annotations and no output schema, it does not disclose authentication requirements, not-found behavior, or response shape; this is minimally viable but not rich.

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 compact sentence with the action front-loaded and the endpoint appended; there is no filler or repeated information. It earns its place without needing expansion.

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 two-parameter GET, the description plus schema is minimally viable. Yet with no output schema or annotations, the agent is left without explicit return-shape, not-found, or authorization 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?

Schema description coverage is 50%: extraQuery is documented in the schema, while id has only a type. The description adds the meaningful fact that id is a path parameter via /reactions/{id}, but provides no format or constraints beyond 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 pairs the verb 'fetch' with the resource 'reaction' and gives the exact endpoint, so the operation is unambiguous. It does not, however, contrast with sibling tools such as create_reaction or other get_* tools, so it stops short of full differentiation.

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?

No alternative tools or when-not-to-use conditions are named; the only guidance is the GET endpoint, which implies the tool is for retrieving a single reaction by ID. This is usable but implicit rather than explicit.

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