ghl_calendar_service_booking_delete

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description aligns by stating 'Delete' and adds useful behavioral context such as the HTTP endpoint and required OAuth scopes (calendars/events.write). No contradictions exist.

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 concise, consisting of three short lines that convey the action, endpoint, and OAuth scopes. It is efficiently structured with no unnecessary information.

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 simple delete operation with one parameter, the description is sufficiently complete. It includes the endpoint and OAuth scopes, which are helpful for execution. No output schema is needed, so no gaps remain.

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 input schema fully describes the single parameter (bookingId) with type, example, and description. The description does not add additional parameter semantics beyond the schema, so baseline 3 is appropriate.

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 'Delete Service Booking' and 'Delete a service booking by ID', which explicitly identifies the verb (delete) and resource (service booking). Among siblings, there are distinct create, get, list, update, and delete variants, making this tool easily distinguishable.

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 states the basic operation (delete by ID) but does not provide explicit guidance on when to use this tool versus alternatives like updating or listing bookings. Usage is implied by the name and operation, but no when-to-use or when-not-to-use context is given.

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