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

Annotations already declare readOnly, non-destructive, closed-world, so the bar is lower; the description still adds real value by naming the auth scope required and by cataloguing the returned fields (public_url, embed_snippet, version) in the absence of an output schema. It does not cover error/not-found behavior, keeping it below a 5.

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?

A single front-loaded sentence with the verb first and the payload enumeration after. The long field list is the one place it thickens, but it substitutes for a missing output schema, so it mostly 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?

For a two-parameter read tool with no output schema, the description supplies the two things an agent would otherwise lack: what comes back and what permission is needed. The parameter semantics are fully covered by the schema.

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 coverage is 100% and both parameters carry their own descriptions (id from booking_status pages[].id, site from list_sites), so the schema does the work. The description adds nothing about parameter formats or constraints; 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?

States a specific verb and resource ("Read one booking page") plus the scope of what is returned. The enumerated settings make it clearly distinct from booking_page_update/booking_page_create and from the plural listers like booking_status.

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 single-page settings retrieval and discloses the required scope (bookings:read), but never says when to prefer this over booking_status, get_booking_resource, or booking_slots. The id-provenance hint lives only in the schema, not the description.

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