send_confirmation_email

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the '(mock implementation)' trait, signaling no real email is sent, which is real value beyond the schema; however it says nothing about idempotency, behavior on an invalid bookingId, or error/return semantics.

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?

A single short sentence with zero waste; the action and target are front-loaded and the parenthetical mock note is compact. Nothing needs trimming.

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 simple one-parameter tool with no output schema and no annotations, the description covers the essential purpose and the mock nature, but omits error behavior and whether calling it is idempotent or conditional on booking state.

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?

The single parameter (bookingId) has 100% schema description coverage, so the schema already documents it fully. The description adds no format, source, or validation meaning beyond what the schema provides, so the baseline of 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?

The description states a specific verb ('Send') and resource ('booking confirmation email') with the target recipient ('passenger'), which is enough for an agent to identify it accurately. It does not name or contrast itself with any sibling tool, though its purpose is naturally distinct from the booking/flight search siblings.

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?

There is no guidance on when this tool should be invoked, no prerequisite (e.g., must follow a successful book_flight or a confirmed booking), and no exclusions or alternatives mentioned. The agent must infer that it belongs after a booking is created.

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