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

With no annotations, the description carries full transparency burden. It discloses that services are listed for every venue, including those without online booking, and explains the bookableViaMcp flag: when false, id is null and cannot book via create_booking, advising to use bookingUrl instead. This fully discloses behavioral traits.

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?

The description is a single paragraph of moderate length, but every sentence adds value. It is front-loaded with purpose, then explains parameter usage, then output fields and edge cases. It could be slightly more concise by splitting into bullet points, but it is well-structured and efficient.

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?

Given the tool's complexity (dual mode, edge case with non-bookable services) and absence of output schema, the description is highly complete. It covers both modes, the output fields (name, description, price, duration, bookableViaMcp), and the crucial edge case handling. No significant gaps remain.

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?

Although schema coverage is 100%, the description adds rich semantics: it explains place_slug's source (search_places) and the effect of providing vs. omitting it, including the strong recommendation to use it. This goes beyond the schema description, providing critical context for correct usage.

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?

The description clearly states it lists a venue's services with price and duration. It specifies the resource (venue's services) and action (list), and distinguishes between two modes (with and without place_slug). This is specific and helps differentiate from sibling tools like create_booking or get_availability.

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 gives explicit guidance: pass place_slug from search_places to list venue services (the common case), and explains that omitting it lists directory's own services (rare). It also notes that only the place_slug form works with create_booking, providing clear when-to-use and when-not-to-use instructions.

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