github_reactions_create_for_issue

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

No annotations are provided, so the description must fully convey behavioral traits. It states 'Create reaction' implying a write operation, but it does not disclose that it likely requires authentication, whether it can modify existing reactions, or the effect of duplicate reactions. The description lacks sufficient behavioral context.

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 sentence and concise, but it is so brief that it omits essential details. It is not verbose, but the lack of structure (e.g., separating purpose from usage) makes it less helpful.

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?

There is no output schema, and the description does not explain what the tool returns (e.g., the reaction object). With 4 parameters, no annotations, and no output schema, the description is incomplete. It should at least mention that the body should contain a 'content' field specifying the type of 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 100%, so the schema already explains parameters. The description adds no information about parameters, such as the required 'owner', 'repo', 'issue_number', or the structure of the 'body' object. With high schema coverage, a score of 3 is appropriate.

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 'Create reaction for an issue' clearly states the verb (create) and resource (reaction on an issue). It distinguishes from sibling tools like github_reactions_create_for_issue_comment by specifying the target as an issue. However, it lacks specificity about what a reaction entails (e.g., emoji type), making it slightly vague.

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 guidance on when to use this tool versus alternatives. Sibling tools exist for other resources (commit comment, pull request review comment, release), but the description does not mention context or exclusions. An agent would have to infer usage from the tool name alone.

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