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

Beyond the annotations, the description discloses meaningful runtime behavior: routing through the SMB's native booking system with fallback to voice AI or web form, async execution via get_outcome, and cost/latency characteristics. It does not detail side effects beyond cancellation, and the mention of 'hold' and 'confirm' is not reflected in the action enum, but the added behavioral context is substantial.

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 description is longer than average but well structured with labeled sections: examples, WHEN TO USE, WHEN NOT TO USE, COST, LATENCY, and EXECUTION. The main purpose is front-loaded, and the sections earn their place by giving practical invocation and routing context. A small amount of redundancy exists, such as the verified smb_id requirement appearing more than once.

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 provides strong operational context: prerequisites, alternatives, cost, latency, and async behavior. However, there is no output schema and the description does not explain the result shape, what availability lookups return, or how nested objects like requested_time and customer should be populated. For an 8-parameter tool with nested objects, this leaves noticeable gaps despite the otherwise rich context.

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 only 25%, so the description needed to compensate, but it only lightly does so. The examples map three natural-language requests onto smb_id, action, and service, yet the reschedule and cancel examples omit the required existing_appointment_id parameter. There is no guidance for requested_time, customer, notes, or how the action enum values relate to the full request flow.

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 opening line clearly names the resource (appointments with an SMB) and lists concrete actions such as book, reschedule, cancel, and check availability. The example queries reinforce what the tool does in practice. It is slightly less crisp than a single-purpose tool because it is an umbrella for several appointment operations and does not explicitly distinguish itself from siblings like check_booking_link or call_business.

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 includes an explicit WHEN TO USE section and a WHEN NOT TO USE section that names alternatives: find_business and verify_business. It also warns against bulk scheduling and emphasizes the verified smb_id prerequisite. This gives the agent clear decision rules for selecting this tool over alternatives.

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