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

Despite no annotations, the description discloses key behaviors: services are listed for every venue, even those without online booking; the bookableViaMcp field and its implications (null id, alternative booking method). It covers return fields and edge cases, though it omits details on rate limits or pagination, which are not critical for this read-only 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?

The description is a single, information-dense paragraph that front-loads the purpose. While it is concise and every sentence adds value, a bulleted structure could improve readability. No wasted words.

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 fully explains return fields (name, description, price, duration, bookableViaMcp) and covers edge cases (non-bookable venues, directory vs venue services). For a list tool with one parameter, this is comprehensive and leaves no gaps.

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?

Input schema has one optional parameter with good description (100% coverage). The description adds value by explaining the source (from search_places), the two outcomes, and that serviceId from this form works with create_booking, enhancing the semantic meaning 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?

Description clearly states 'List a venue's services — what it offers, with price and duration.' It specifies the verb 'list', the resource 'venue's services', and distinguishes between the two modes (with and without place_slug), effectively differentiating from sibling tools like get_availability and create_booking.

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 explains when to use each form: 'pass place_slug... that is what you want in almost every case' and omitting it lists directory services 'which most sites do not have.' Provides clear context and alternatives, such as using bookingUrl when bookableViaMcp is false.

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