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

Annotations already indicate this is a mutating, non-idempotent action. The description adds useful behavioral details: it executes immediately, emails the customer, creates a Zoom meeting for online bookings, and fails on double-booking. This goes beyond what annotations alone convey.

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?

Four sentences, each carrying distinct value: what the tool does, immediacy, prerequisite data source, and conditional field requirements. No filler or repetition of schema details.

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?

Given this is a 10-parameter mutation with an output schema present, the description covers the critical behavioral constraints and prerequisites. It could have mentioned the response/return behavior, but an output schema exists, so that is not required. The main remaining gap is minor.

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 50%, so description helpfully compensates by explaining the relationship between meetingType and customerEmail/customerPhone, and instructs where to source teamMemberId and timezone. It does not explain title, customerName, or meetingType, but those are largely self-evident from the schema.

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 action ('Creates a new appointment'), the target system ('connected Nexwin account'), and a secondary effect ('emails the customer a confirmation'). It clearly differentiates from sibling tools like cancel_booking and reschedule_booking by focusing on creation.

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?

Provides concrete guidance: get teamMemberId and timezone from list_team_members first, use customerEmail for online bookings, and use customerEmail or customerPhone for in-person bookings. It also warns about failure when the team member is already booked. It does not explicitly name alternatives, but the operational context is clear.

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