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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description is not burdened there. It goes beyond them by disclosing result ordering, the exact fields returned, and the meaning of two trust-relevant fields: source (property_manager = the site's own manager) and commercial (paid placement), which matters for how an agent weighs results.

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?

Three sentences, front-loaded with the action and scope before the field inventory and the response shape. The middle sentence is a long enumeration of fields, but each item (source, commercial) carries meaning rather than padding.

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 takes on the return-value job and does it: it names the record fields and the envelope (total, per-category counts, nextCursor). Given full schema coverage, a single site-scoped list tool is adequately covered, with only minor gaps such as default limit or pagination mechanics.

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 description coverage is 100%, so parameter meaning is already carried by the schema, making 3 the baseline. The description adds nothing parameter-specific beyond noting the site scoping and that nextCursor comes from the answer, which only lightly reinforces the cursor parameter.

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 ("Lists things to do near one Booking Bench site"), plus scope (single site) and ordering (alphabetically), which separates it from get_activity. It does not explicitly contrast with list_events, so the sibling boundary is only inferable from the resource noun.

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 implied: the agent needs a siteSlug (documented in the schema as coming from list_sites) and this is a browse/list operation. There is no explicit when-to-use vs get_activity or list_events guidance, and no statement about when not to use it.

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