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

Annotations already mark the tool as destructive and readOnly=false. The description adds useful behavioral context beyond those annotations: it requires an authenticated business owner, explains that the client is notified, and clarifies when the different decision states apply. There is no contradiction with the 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?

Three dense sentences with no filler. The audience and scope are front-loaded, the decision states are compactly enumerated, and the parentheticals efficiently attach the relevant parameter meanings. Every sentence earns its place.

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 mutation tool with no output schema, the description covers the essential operational context: who may call it, which decisions are available, when they apply, a precondition, and the client notification side effect. It could be even more complete by mentioning return behavior or error cases, but it is strong enough for an agent to invoke it correctly in most situations.

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 does add meaning by linking 'reason' to decline and 'price' to quote, and it mirrors the decision enum. However, it leaves booking_id unexplained and doesn't cover constraints or required-conditional behavior for reason and price, so the 4-parameter surface is only partially documented.

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 resource (a pending booking) and enumerates the exact decision actions: confirm, decline, quote, complete, no_show. It also scopes the tool to business owners signed in to Awning, which separates it from customer-facing and operator tools. It doesn't explicitly name sibling alternatives, so it falls just short of full differentiation.

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 gives clear context: only for business owners signed in to Awning, and only for pending requests before the visit or for complete/no_show after the visit. It also gives a precondition: confirm with the owner before declining. It does not explicitly state when to use a sibling tool like owner_cancel_booking instead, so it earns a 4 rather than a 5.

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