get_reactions

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

With no annotations provided, the description carries the full behavioral burden. It implies a read-only operation but does not disclose the return shape (a list of reactions, their fields), whether order is guaranteed, or how empty results are handled for nodes with no reactions.

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 front-loaded sentence with zero waste. It is concise, though bordering on under-specification given the missing behavioral context rather than being genuinely economical.

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 tool with one required parameter, no output schema, and no annotations, the description should say more about what a 'reaction' contains and what the caller receives. It omits any sense of the return structure or the semantics of a prototype reaction.

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% for the single nodeIds parameter. The phrase 'from nodes' (plural) reinforces that multiple node IDs are accepted, adding marginal value over the schema, but no format or constraint details are given.

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?

States a specific verb ('Get') and resource ('all prototype reactions') plus the source ('from nodes'), which is a distinct resource from set_reactions/clear_reactions. However it offers no explicit differentiation from sibling tools like clear_reactions or get_annotations, so the agent must infer the distinction.

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 guidance on when to use this tool versus alternatives such as clear_reactions, set_reactions, or upsert_reaction. The plural 'reactions' implies a bulk read, but no conditions or exclusions are stated.

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