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

Annotations supply only destructiveHint=true, so the description carries the load and does it well: it discloses the customer-facing email side effect and its default-off behavior, the no-message property-only mode, and the compulsory-custom-field prerequisite for closing. These are the highest-risk, least-obvious behaviors of this mutation.

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?

Four dense sentences, front-loaded with the core action and the most surprising constraint (email gating) placed early. The trailing REST endpoint line is harmless but not something an agent needs to select or invoke the tool.

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 16-parameter destructive mutation with no output schema, the description covers the important behavioral prerequisites and side effects. It omits anything about return payload, error conditions, or partial-update behavior, but with no output schema that burden is lower.

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 documents every parameter including update_customer, custom_fields, and the completion requirement. The description reinforces update_customer and the closing constraint but adds little syntax or format detail beyond what the schema provides, matching the baseline 3.

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 gives a specific verb+resource ('Add an agent reply to a ticket') and immediately broadens it to the property-mutation capability (status, priority, assignee, due date, tags), so the dual nature of the tool is unmistakable. It does not, however, explicitly distinguish itself from close siblings such as happyfox_add_private_note or happyfox_update_ticket_tags, leaving that contrast to inference.

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?

It gives real decision context: the contact is emailed ONLY when update_customer is true (default false), and with no message the call degrades to a pure property update. It also warns that moving to a completed status may require compulsory custom fields. It stops short of naming an alternative tool for the internal-note case.

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