create_reaction

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

With no annotations, the description carries the full behavioral burden and only reveals that this is a POST/add operation. It does not disclose whether duplicate reactions are allowed, what authentication or permissions are required, what side effects occur, or what the response looks like.

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 one concise sentence that front-loads the action and includes the endpoint for extra clarity. There is no filler and no repetition of schema content.

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 creation endpoint, the description and schema together are mostly usable: required path parameters are identifiable and the body field is explained. However, without annotations, output schema, and a full enumeration of valid reference types are all missing, leaving gaps around response format and allowed values.

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?

The schema documents body, extraBody, and extraQuery, while refType and refId lack schema descriptions. The description partly compensates by embedding refType/refId in the URL path and giving examples of acceptable refType values, but it does not define refId semantics or constrain refType beyond two examples.

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 states a specific action ('Add a reaction') and target ('reference data object'), with concrete examples 'Note' or 'ThreadedReply' plus the endpoint POST /reactions/{refType}/{refId}, so the purpose is clear. It is distinct from siblings like create_note or get_reaction, though it does not explicitly contrast with any sibling.

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 or when not to use it. The phrase 'corresponding reference data object' gives only generalized context, but no exclusions, prerequisites, or sibling routing are provided.

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