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?
No annotations are provided, so the description carries the full burden. It mentions return fields (name, profile URL, category, metadata) but does not disclose any behavioral traits such as idempotency, safety, side effects, pagination behavior, or authentication requirements. The default limit is implied by the schema but not in the description.
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 sentence that conveys the tool's purpose and return fields without any wasted words. It is front-loaded and efficiently uses space.
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 simple input schema with one optional parameter, the description explains what the tool returns. However, it does not mention pagination behavior beyond the limit parameter, ordering, or whether the list includes all profiles. For a listing tool, this is decent but could be more complete.
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% for the single 'limit' parameter. The tool description does not add extra meaning to the parameter beyond what the schema already provides, but it does provide context about the return fields, helping understand the parameter's purpose. Baseline 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 clearly states the tool lists solo service-provider profiles on the site, distinguishing them as businesses without a fixed physical location with relevant examples (dog walkers, tutors). This verb+resource combination is specific and differentiates from sibling tools like list_blog_posts or list_products.
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 implies this tool is for listing solo service-provider profiles, but it does not explicitly state when to use it versus other list_* tools, nor does it provide exclusions or alternatives. The context is clear but lacks explicit guidance.
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.
Tools are mostly distinct with clear descriptions. Some overlap in actions that require user to click a link (create_booking, create_checkout, request_reservation, etc.), but each targets a different domain (booking, store, restaurant, event tickets, RSVP). Minor ambiguity possible but descriptions clarify.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_booking, get_availability, search_places). No deviations or mixed conventions.
28 tools is slightly high for a neighborhood directory, but each serves a specific function (search, booking, events, movies, offers, etc.). The scope justifies the count, though some tools like list_blog_posts and list_faqs might be considered niche.
The tool set covers search, place details, categories, menus, events, movies, offers, booking, and forms. Missing update/delete operations for places or user management, but these are likely out of scope for a read-only directory. Core queries and actions are well-supported.
