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

Beyond the annotations, the description discloses that this operation relies on server context, requires one-time authorization, and must reuse an idempotency key for safe retries. These are meaningful behavioral details not present in readOnlyHint, idempotentHint, or destructiveHint. No contradiction with annotations is present.

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?

Three dense sentences, each earning its place: the critical invocation guardrail, the server-context rule, and the retry rule. Information is front-loaded and there is no filler.

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?

The description gives strong operational guardrails and enough context for safe invocation, especially with the output schema available. It falls slightly short on documenting several required parameters, but the required context is largely conveyed through the schema, enum, and clear guardrail language.

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 0%, so the description must compensate. It clarifies the idempotency key's retry semantics and warns against passing server-context fields, but it does not explain source, campaign_id, correlation_id, anonymous_session_id, or how to obtain the booking_authorization_token. Coverage is partial, not comprehensive.

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 title and tool name clearly identify this as creating a confirmed service booking, and the description adds the precise context of the protected final card after user confirmation. It is distinguishable from siblings like cancel or reschedule, though the description does not explicitly name an alternative.

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 explicitly states when this tool may be used: only from the protected final card with one-time authorization after the user presses Confirm. It also gives a clear negative rule: do not pass or reconstruct server-context fields, and explains safe retry behavior with the idempotency key.

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