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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's added value is naming the composite payload (services, hours, staff, rules, blocked time), which tells the agent this is a bundled configuration read rather than a list. It says nothing about behavior when booking is unconfigured, about size/truncation of the blocked-time section, or about ordering.

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?

One sentence, front-loaded with the verb and the returned content, with zero filler. Everything stated earns its place and nothing is buried.

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 single-parameter read with full annotation coverage and no output schema, enumerating the returned sections largely substitutes for the missing output schema. It would be complete if it clarified the tool's relationship to list_bookings and to sites without booking enabled.

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 parameter with 100% schema description coverage (site slug or id), so the schema already carries the semantics and the description correctly needs to add nothing. The phrase "for a site" echoes the schema without extending it. 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?

A specific verb ("Show") plus a clearly scoped resource ("booking setup ... for a site"), with the payload enumerated as services, hours, staff, rules and blocked time. It implicitly contrasts with the write-side siblings set_booking/update_booking and the collection tool list_bookings by framing this as configuration retrieval, but never names an alternative explicitly.

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?

Usage is only implied: by describing the returned configuration, the description signals 'use when you need a site's booking configuration' rather than actual bookings. There is no explicit when-to-use statement, no mention of list_bookings versus this tool, and no stated prerequisites (e.g. does the site need to be published or have booking enabled?).

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