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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real context beyond that: the read payload is round-trip compatible with update_booking_unit, which tells the agent it can read-then-write with the same shape. It does not discuss auth or pagination, but neither is implied by the tool.

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?

Two sentences, front-loaded with the payload scope and followed by the usage condition. Every clause earns its place; nothing is repeated from the title or schema.

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?

An output schema exists, so return values needn't be spelled out, yet the description still signals the payload shape as a write-compatible contract. Purpose, timing, and round-trip relationship to update_booking_unit are all covered for a simple two-param read.

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 (business, bookingUnitId) are documented in the schema, including their provenance (page handle, from list_catalog). The description adds no parameter-level detail beyond the schema, so the 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?

States a specific verb (read) and resource (one offering/booking unit), and enumerates the substantive fields it returns — schedule, timezone, price, meeting setup, questions, images, policy. The reference to 'the shape update_booking_unit takes' implicitly distinguishes it from the write sibling, though no other read tool is explicitly contrasted.

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?

Gives a clear call condition: read before changing an offering, and to answer questions about it. This ties it directly to update_booking_unit as the natural predecessor. It lacks an explicit when-not / alternative clause, so it falls short of a 5.

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