Returns service categories and types available for a given postal or zip code, accounting for location coverage and seasonal availability. Call this after collecting the customer's postal code to determine what services to offer.
| Name | Required | Description | Default |
|---|---|---|---|
| postalCode | Yes | Customer postal or zip code (e.g. "K1A 0A1" or "90210"). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description covers location and seasonal constraints but lacks details on idempotency, error handling, or rate limits. Adequate but not comprehensive.
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 concise sentences: first states functionality, second gives usage guidance. No extraneous 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?
Simple tool with one parameter; description provides sufficient context. Lacks return format details but overall adequate.
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 covers the parameter fully; description adds value by explaining why postalCode is used (to check coverage and availability), going 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?
The description clearly states the tool returns service categories and types based on postal/zip code, mentioning location coverage and seasonal availability. It distinguishes well from siblings like calculate_quote and create_order.
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 says to call after collecting postal code to determine services to offer, providing clear context. Does not include when not to use, but sibling differentiation is clear.
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 has a clearly distinct purpose: quoting, ordering, job cancellation, job rescheduling, profile retrieval, service availability lookup, scheduled jobs listing, and current datetime. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case, such as calculate_quote, cancel_job, get_profile, etc. No mixing of conventions.
8 tools is well-scoped for a home services booking server. It covers the essential customer-facing operations without being too few or excessive.
The tool set covers the core workflow: checking services, getting quotes, creating orders, managing jobs (view, cancel, reschedule). Minor gap: no tool to update profile or payment method, but the surface is largely complete for the stated purpose.
