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

With readOnlyHint=false and idempotentHint=false, an agent might expect real side effects; the description explicitly corrects this by stating bookings are test bookings, no customer is contacted and no email is sent. It also discloses quota behavior ('conversation and message limits') and enumerates what comes back, which the annotations do not cover.

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 short sentences, front-loaded with the action and return payload, each carrying distinct information (action, conversation continuation, side-effect disclaimer, limits). No filler or redundancy.

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?

There is no output schema, and the description compensates by naming the reply, actions and remaining test budget. It omits error behavior for a non-ready preview and any auth expectations, which are minor gaps for this tool.

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 baseline is 3. The description adds only marginal meaning beyond the schema, mainly implying the `preview` value must reference a ready preview; it does not explain formats or the handle-vs-link distinction further.

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 and resource: sends one simulated customer message to a preview and returns the reply, actions and remaining budget. The 'ask' action is distinguishable from the sibling verbs build_/get_front_desk_preview, though the description never names those siblings explicitly.

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?

Conveys the prerequisite that the preview must be 'ready' and that omitting `conversation` starts a fresh test thread versus continuing an existing one. It gives clear operating context but no explicit when-not-to-use guidance or named alternatives.

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