list_work_package_reactions

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

No annotations are provided, so the description carries the full burden. It clarifies the parameter format (internal ID vs display ID) but does not disclose behavioral details such as pagination, response structure, required permissions, or whether reactions are aggregated per comment or globally. This is a basic read-only tool, so the missing details are not critical but leave some gaps.

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 two sentences: the first states the purpose, and the second explains the only parameter. It is front-loaded, concise, and every sentence earns its place with no redundancy.

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 one-parameter list tool with no annotations and no output schema, the description adequately covers the primary use case and parameter semantics. It could mention response content or limitations, but the low complexity makes the description sufficient for an agent to select and invoke the tool correctly.

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 only provides a bare anyOf integer/string with zero description coverage. The description adds crucial meaning by explaining work_package_id can be an internal id (e.g., 952) or display_id (e.g., 'PROJ-51') and explicitly notes it is not a UI display number. This fully compensates for the schema's lack of description.

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 emoji reactions across a work package's comment activities, using the specific verb 'List' and resource 'emoji reactions'. It distinguishes itself from sibling tools that handle file links, watchers, or activities.

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 implies this tool is used when you need emoji reactions for a work package's comments, which is clear from the purpose. It does not explicitly name alternatives or when-not-to-use, but the context is sufficiently clear given the sibling tool names.

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