list_merge_request_note_emoji_reactions

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

The description adds little beyond the annotations: readOnlyHint=true already signals a safe read operation. It does not disclose pagination, rate limits, or that 'all' may be subject to server limits, leaving a gap in 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?

Two sentences, both front-loaded with essential information. No redundant words or structural issues. Efficiently communicates purpose and key usage nuance.

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?

While annotations cover read-only and schema covers parameters, the description omits what is returned (e.g., emoji objects, attrs). Given no output schema, this omission reduces completeness for a list tool.

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 baseline is 3. The description echoes the discussion_id nuance already in the schema, adding marginal value. No new parameter semantics beyond what the schema provides.

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 clearly states the tool lists all emoji reactions on a merge request note, with specific instruction about discussion_id for thread replies. It effectively distinguishes this from sibling list tools like list_merge_request_emoji_reactions or list_issues.

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?

The description provides a usage nuance (discussion_id for thread replies) but does not indicate when to use this tool over alternatives like list_issue_note_emoji_reactions or list_merge_request_emoji_reactions. No explicit when-not-to-use guidance.

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