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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior beyond annotations: it discloses the 30-day maximum range, 25-result limit, and the specific fields included in each booking (appointmentId, teamMemberId, ISO startTime/endTime, timezone), plus the connected-account requirement.

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 concise sentences front-load the core purpose and limits, then add relation to sibling tools and account requirement. No filler or redundant restating of the title or schema. 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?

Given the tool's moderate complexity, the presence of an output schema, and rich annotations, the description covers the essential operational context: purpose, date range limits, result cap, key fields, sibling-tool usage, and account prerequisite. No critical information needed for correct invocation is missing.

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 schema already provides descriptions for startDate and endDate ('YYYY-MM-DD, business-local'), giving 67% coverage. The description adds the 30-day max range constraint and clarifies the result fields, which aids parameter interpretation, but it does not address the optional status parameter's meaning or filtering behavior beyond the enum in the schema. Overall, it adds some value but the schema still carries the main parameter burden.

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 ('Lists'), a clear resource ('appointments/bookings in a date range'), and adds the account scope ('connected Nexwin account'). It also distinguishes the tool's output by noting fields needed for sibling tools reschedule_booking and cancel_booking, so an agent can identify its role without opening the schema.

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 clearly implies when to use this tool: to retrieve bookings in a date range, especially when needing appointmentId and teamMemberId for reschedule_booking or cancel_booking. It also notes the 'Requires a connected account' prerequisite. It does not explicitly state when not to use it or name an alternative for listing bookings, but the context is clear enough.

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