List solo service-provider profiles on this site — businesses without a fixed physical location (e.g. dog walkers, tutors, personal trainers). Returns name, profile URL, category, and any available metadata (age, height, etc.).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max profiles to return (default 50). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the return fields (name, profile URL, category, metadata) and clearly defines the profile scope, which is valuable behavioral context. However, it omits details about pagination, sorting, or authentication, which are minor for a listing tool but could be useful.
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 two sentences, front-loaded with the action, and every sentence contributes value: the first defines the resource, the second lists return fields. There is no fluff or redundancy, making it concise and well-structured.
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 simplicity (one optional parameter, no output schema, no annotations), the description covers the essential return values and scope. It does not mention default limit or pagination, but the schema covers the limit default. It is complete enough for an agent to understand what this tool does and what it returns, though some minor behavioral details are omitted.
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?
The input schema has one optional parameter (limit) with a description ('Max profiles to return (default 50)'), yielding 100% schema coverage. The tool description adds no additional meaning for this parameter beyond the schema, so the baseline score of 3 is appropriate.
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 uses a specific verb ('List') and identifies the resource ('solo service-provider profiles') with a clear definition and examples (dog walkers, tutors, personal trainers). This distinguishes it from sibling tools like list_products or search_places, which target physical locations or other entity types.
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 clearly defines the scope: profiles for businesses without a fixed physical location. This context implies when to use the tool, but it does not explicitly state when not to use it or mention alternatives like search_places for physical locations. The clarification is strong enough for an agent to infer usage, but it lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action (e.g., create_booking vs create_checkout, reserve_event_tickets vs rsvp_event), and descriptions provide clear boundaries. Even closely related tools like list_booking_services and list_pricing_plans are differentiated by context.
All 26 tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, search_, etc.), with no mixed conventions or vague verbs. This makes the tool set predictable and easy to navigate.
At 26 tools, the set is on the heavy side and exceeds the typical well-scoped range, but the diversity reflects a multi-featured directory covering bookings, events, store, reviews, forms, and more. Each tool appears to serve a distinct purpose, so the count is borderline rather than excessive.
The surface covers the core user workflows: search, view details, book services, reserve/RSVP events, request reservations, submit forms, and browse content. Minor gaps exist (e.g., no cancellation/update for bookings, no full blog post body), but these are workarounds and not critical for a consumer-facing directory.
