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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds substantive domain behavior instead — the meaning of partyMode values, what partyMax/tableSize imply, and that a service with chargeWhenBooking is paid in full via the business's own Stripe on the public page. It says nothing about error modes or freshness of the settings, which is the remaining gap.

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?

Content is mostly relevant, but it is delivered as one sprawling sentence with deeply nested parentheses that is hard to scan; the actionable instruction ('Read it before...') is buried at the end rather than front-loaded. Several parenthetical definitions arguably belong in the settings schema rather than the tool description.

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?

With no output schema, the description carries the full burden of explaining return values and it does so thoroughly — every major section of the settings payload (services, resources, booking form, rules, calendar, public URL) is accounted for, plus the implications of paid services.

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?

There is a single optional parameter whose schema description already covers 100% of the semantics (defaults to the connection's scoped workspace). The prose adds no further information about workspaceId, so the baseline 3 applies.

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 makes clear this returns the workspace's appointment configuration by enumerating the contents (services, resources, booking form, rules, calendar connection, public page URL). The action verb ('get') is only implicit in the phrase 'How appointments are set up in this workspace', but the scope is unambiguous and pairs naturally with the sibling 'update_booking_settings'.

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?

It gives a concrete precondition — 'Read it before offering or booking anything, and before changing the setup' — and names the alternatives for mutation (booking service and booking resource tools, update_booking_settings). It stops short of stating when not to call it (e.g., use get_booking_availability for slot lookups).

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