search_therapists

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

Annotations already declare the safe read-only, idempotent, open-world profile, so the bar is lower. The description adds genuinely useful behavior beyond them: exactly one website page is returned per call, how to advance pages, and the caveat that reported availability is not a booking guarantee.

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 core action and result contents, then filter sourcing, then pagination and the availability caveat. No filler or repetition.

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 an output schema present, return values need no explanation, and the description covers the filter-value convention and pagination loop. Slightly thin on how radius interacts with location or on result ordering, but nothing an agent needs in order to call it 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 coverage is 100%, so the baseline is 3, but the description adds the cross-cutting convention that filter parameters accept either an ID or an exact German label sourced from get_search_filters, which is the key non-obvious semantic for the eight filter params. It does not add anything for location, radius_km, or page 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?

States a specific verb and resource ('Search public therapist listings') plus what the result set contains (contact details, distances, source URLs, pagination). This clearly separates it from sibling retrieval tools like get_therapist, compare_therapists, and get_shortlist.

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 routes the agent to get_search_filters for filter IDs/labels and explains the pagination protocol (one page per call, follow next_page_url). It gives clear context for use but names no explicit when-not-to-use case or alternative search path.

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