ghl_calendar_service_booking_list

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

Annotations already declare read-only and idempotent. The description adds key behavioral detail: no pagination (limit/offset) and results bounded by required date range. Does not mention rate limits or response size but sufficient with 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?

Description has 5 sentences but feels scattered: opens with parameter format, then title, then description, then endpoint and scopes. Title line 'Get Service Bookings' is redundant. Could be more organized.

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 5 parameters, no output schema, and annotations, the description covers required filters, optional filter, date range bounding, and OAuth scopes. Lacks mention of response format but reasonable for a list tool.

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 covers all 5 parameters with descriptions and examples. The description reiterates startTime/endTime as epoch milliseconds and notes no limit/offset, but adds little beyond schema. Baseline 3 applies due to full schema coverage.

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 clearly states it retrieves service bookings for a location within a date range, with an optional service location filter. It distinguishes from sibling tools (e.g., get, create) by focusing on listing.

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 implies usage for filtering by date range and location but does not explicitly contrast with alternative tools or specify when not to use it.

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