list_wedding_marketsList the countries, regions and vendor categories Wedyesday supports, with the exact values to pass to the other Wedyesday tools. Call this first when you do not already know a valid country code, region slug or vendor category.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | Optional ISO country code (AU, US, GB, NZ, IN). Supply it to list that market's regions. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral context beyond annotations by explaining the output acts as a canonical source of exact values for downstream tools.
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?
Two sentences, no fluff, and the intended behavior is introduced immediately. The description is compact while still conveying both what is listed and when to invoke the tool.
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?
The tool has one optional parameter, 100% schema coverage, and strong annotations. The description covers output scope and usage context, and no further detail is likely needed for an agent to invoke it correctly.
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 already fully describes the optional country parameter including ISO codes (AU, US, GB, NZ, IN) and its behavior. The description adds no new parameter-specific information, so baseline 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 countries, regions, and vendor categories supported by Wedyesday, and it explicitly notes that these are exact values to pass to other tools. This verb-resource-scope combination makes it distinct from sibling tools like search_wedding_vendors.
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 an explicit when-to-use rule: call this first when you do not know a valid country code, region slug, or vendor category. It does not explicitly mention when not to use it, but the 'call first' directive provides clear context that other tools depend on this reference data.
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 and action: planning, workspace link creation, cost guide, market listing, vendor search, dashboard, budget, guest list, and task lifecycle. There is no meaningful overlap or risk of selecting the wrong tool.
Most tools follow a clear verb_noun pattern, with account-scoped tools using a 'my' prefix (get_my_wedding_budget, list_my_wedding_tasks) and public tools using plain nouns (list_wedding_markets, search_wedding_vendors). Minor naming deviations like create_wedyesday_workspace_link and get_my_guest_list keep the pattern mostly predictable but not perfectly uniform.
Eleven tools is a well-scoped size for a wedding planning server, covering plan generation, vendor discovery, cost guidance, and personal wedding data. Each tool has a clear purpose and none feel redundant.
The tool set covers the main wedding planning workflows: creating plans, generating workspace links, checking costs, searching vendors, viewing the dashboard/budget/guest list, and managing tasks. Minor gaps exist, such as no task update/delete and no guest management, but core user journeys are supported.