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

With annotations covering the safety profile (mutation, openWorld, non-idempotent, non-destructive), the description adds substantial lifecycle context: the request only reaches the guide after the deposit is paid, the 24h/6h acceptance window, full deposit refund on rejection, and WhatsApp contact exchange after acceptance. It also states a hard prerequisite (fisher's WhatsApp) and an explicit exclusion ("não recebe dados de pagamento"), which an agent cannot infer from the schema or annotations.

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?

The core action and return value are front-loaded, then the acceptance/refund lifecycle, then the edge case of a missing guide_id with its motivating condition. Dense but every sentence carries a distinct fact; only the guide-contact sentence could be trimmed without loss of decision-relevant information.

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 nine-parameter mutation tool with no output schema, the description supplies the return value (payUrl and what the page is for), the full post-request lifecycle, prerequisites, and the no-guide fallback path. Nothing an agent needs in order to decide and call correctly is missing, including what not to send.

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 coverage is 100% with all nine parameters described, so the baseline is 3. The description reinforces only two points already documented in the schema — that whatsapp is required and what happens without guide_id — and adds no format, range, or interdependency detail beyond it.

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?

"Faz o pedido de reserva na iscabox e devolve `payUrl`" names a specific verb (pedido de reserva), the resource (booking), the target system, and the primary return value. This clearly separates it from read-only siblings like find_guides or quote_trip, and an agent knows immediately what changes in the world.

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 explicitly documents the fork in usage: with guide_id the request goes to that guide, without it the iscabox team finds a guide and answers via WhatsApp — including the trigger condition "útil quando find_guides vem vazio". What is missing is a direct comparison with quote_trip (price inquiry before booking), which an agent would plausibly confuse with this tool.

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