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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description goes further by disclosing the `venueClock` return semantics and the non-obvious rule that all later dates resolve against `venueClock.today` rather than the caller's today, plus the deliberate absence of a timezone identifier. It stops short of describing the full shape of the profile payload, but the critical misuse hazard (date/time interpretation) is well covered.

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?

Front-loaded with purpose and the call-ordering rule in the first sentence, then the time-semantics caveat. Slightly longer than strictly necessary, but the second paragraph is not padding: it preempts a real failure mode (off-by-hours bookings) that no structured field communicates.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does: it names `venueClock`, states the result is venue-local time as text with no timezone identifier, and explains how downstream calls should interpret dates. With one fully documented required parameter and clean annotations, nothing an agent needs to call this correctly is missing.

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% and the property description already explains the slug format exhaustively, including the 'not the business name' warning and the booking-link derivation. The description reinforces this by tying the slug back to get_venue's own output, which helps close the loop across calls, but it adds no new format detail beyond the schema.

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?

Opens with a concrete verb and resource: reading a venue's public booking profile, and enumerates what that profile contains (identity, location, bookable services, current local time). It also positions itself against siblings by declaring it must be called first, so an agent can place it in the workflow without opening any schema.

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?

Explicitly states 'Call this first' and gives the reason: other tools need the venue slug, and appointment searches need a service id from here. That is a when-to-use rule plus the dependency ordering, with no inference required.

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