zulip

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Add an emoji reaction' implies a write operation, it doesn't specify permissions required, whether reactions are reversible (though 'remove_reaction' sibling suggests they are), rate limits, or what the output contains. The description adds minimal behavioral context beyond the basic action.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Both sentences earn their place by providing critical information. It could be slightly more concise by integrating the parameter details into the main sentence, but overall it's well-organized and front-loaded.

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?

Given the tool's moderate complexity (2 required parameters, no annotations, but with an output schema), the description is reasonably complete. It covers purpose and parameter semantics adequately. The presence of an output schema means return values don't need explanation, though more behavioral context (like permissions or side effects) would improve completeness for a write operation.

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?

With 0% schema description coverage, the description fully compensates by clearly explaining both parameters: 'message_id' identifies the target message, and 'emoji_name' specifies the emoji format ('without colons') with concrete examples ('thumbs_up', 'check'). This adds essential meaning not present in the bare schema.

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 specific action ('Add an emoji reaction') and target resource ('to a message'), using precise verb+resource language. It distinguishes this tool from sibling tools like 'remove_reaction' (which does the opposite) and 'edit_message'/'send_message' (which modify message content rather than reactions).

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 usage context through the action itself (adding reactions to messages) but provides no explicit guidance on when to use this tool versus alternatives like 'edit_message' for modifying content or 'remove_reaction' for undoing reactions. No prerequisites or exclusions are mentioned.

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