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

Annotations only supply destructiveHint=true, so the description carries most of the burden. It discloses the effect (a message is appended to an existing conversation) and the consequential visibility distinction between a customer-facing reply and an internal note, which is real operational context. It does not cover irreversibility, duplicate-send behavior on repeated calls, or permission needs.

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 sentences, zero filler: the effect and its two modes come first, the endpoint identifier last. Nothing is wasted or buried.

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 mutation tool with no output schema and only a destructiveHint annotation, the description adequately conveys effect and visibility semantics. It stops short of the mutation caveats an agent would want (repeat calls create additional messages, sends are externally visible and not recallable).

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 every parameter including visibility's 0/1 mapping is already documented in the schema. The description's 'customer-facing reply or internal note' simply mirrors the visibility enum values and adds no syntax or constraint beyond the structured data. Baseline 3 applies.

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 ('existing conversation'), and explicitly scopes the two modes (customer-facing reply vs internal note). Combined with the REST endpoint, an agent can distinguish this from reamaze_create_conversation and reamaze_list_messages without opening any schema.

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 phrase 'an existing conversation' implies a slug must already exist, which steers the agent away from create_conversation, and the reply/note split gives context. However, no named alternative or explicit when-not condition is given (e.g. use create_conversation for a new thread, list_messages to read).

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