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

Annotations provide only destructiveHint=true, which the description never addresses or explains. The description does add genuinely useful behavioral context by framing the two modes (customer-facing vs internal note), which matters operationally, but it omits notification behavior by default, staff-vs-customer authoring implications, and any rate or permission constraints.

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 with zero filler; the primary purpose is front-loaded before the endpoint reference. Every clause carries information an agent can use.

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 an 8-parameter tool with full schema coverage and no output schema, the description covers the core purpose adequately and does not need to explain return values. It falls slightly short of complete because it never reconciles the destructiveHint annotation or explains default notification behavior, but nothing critical for invocation is missing.

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 all eight parameters are already documented at the field level, including the visibility enum meaning (0 = regular reply, 1 = internal note) and suppress_notifications. The description's reply-vs-note framing mirrors what the schema already says, adding little beyond the required baseline.

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?

States a specific verb (add a message) and resource (an existing conversation), and elaborates on the two message modes (customer-facing reply or internal note). The word "existing" implicitly separates it from sibling reamaze_create_conversation, and the REST endpoint reference anchors the operation precisely.

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 mentions the two possible message modes, which hints at when each applies, but gives no explicit when-to-use guidance, prerequisites, or comparison to alternatives like reamaze_update_conversation or reamaze_create_conversation. Usage is implied rather than stated.

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