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

Annotations supply only destructiveHint=true; the description adds real behavioral context by disclosing the note is internal-only (never visible to the contact) and that the call can also alert agents and rewrite status, priority, assignee, due date and tags. That mutation scope corroborates the destructive hint, though reversibility and alert semantics are not spelled out.

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 tight sentences: purpose and the critical internal-only distinction come first, side effects second, endpoint last. No filler.

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 12-parameter, nested-object mutation tool with no output schema, the description covers purpose, the internal-only nature and the full set of side effects. It omits return behavior and any note on compulsory custom fields on close (left to the schema), leaving a minor gap.

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% across 12 parameters, so the schema already documents html/plaintext, alert codes, ids, due-date formats and custom_fields. The description only recaps that alert/status/priority/assignee/due_date/tags can be set and adds no syntax or value beyond the schema, which is the expected baseline here.

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?

Specific verb+resource (add an internal/private note to a ticket) with the key qualifier "never sent to the contact," which immediately separates it from the customer-facing happyfox_add_staff_reply. It also enumerates the secondary mutations (status, priority, assignee, due date, tags) so an agent knows the call does more than append text.

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?

"Internal note (never sent to the contact)" gives clear selection context against the reply sibling, but the alternative is not named and there are no explicit exclusions or prerequisites. This is clear context without routing language.

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