get_washbodega_servicesReturn verified public Wash & Fold and pickup/delivery availability in English or Spanish. Read only; never collects personal data or creates an order.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | en-US |
| Name | Required | Description | Default |
|---|---|---|---|
| locale | Yes | ||
| services | Yes | ||
| sourceUrl | Yes | ||
| boundaries | Yes | ||
| publishedAt | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is pre-covered. The description adds useful behavior beyond that: the data is 'verified public', and the tool 'never collects personal data or creates an order', giving extra clarity on privacy and side-effect expectations. No contradiction with the annotations.
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 short sentences with no filler. The primary action and resource are front-loaded, and the read-only/privacy qualifier follows immediately. Every word earns its place.
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 param), rich annotations, and existing output schema, the description is fully sufficient. It explains what data is returned, the language options, and the side-effect profile. Nothing critical is missing 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 schema has no descriptions for its single parameter, so the description must compensate. 'In English or Spanish' adds meaning to the locale parameter, clarifying that the enum values control the response language. The parameter is optional and self-explanatory further, but the description could have explicitly mapped locale to language for full clarity.
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 states a specific verb ('Return') and resource ('verified public Wash & Fold and pickup/delivery availability'), which clearly distinguishes it from siblings focused on location hours, ordering handoff, pickup/delivery policy, and pricing. The 'in English or Spanish' phrase also clarifies the locale scope without confusing it with other service resources.
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?
It gives clear context for when to use the tool: when needing verified public availability information. It also provides a when-not by saying it never creates an order, signaling not to use it for order-related tasks. However, it does not explicitly name or contrast the sibling tools, so the routing guidance is slightly less direct.
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 clearly distinct information area: hours/location, ordering link, delivery policy, pricing, and services. There is no meaningful overlap between tool purposes, and the descriptions reinforce these boundaries.
All tool names follow the exact pattern get_washbodega_<topic> with consistent snake_case verb-noun naming. The naming is predictable and makes the tool set easy to navigate.
Five tools is a well-scoped size for a read-only service discovery server. Each tool covers one necessary public information category without excess or redundancy.
For the stated purpose of service discovery, the tool set covers all key public-facing information: location hours, ordering link, pickup/delivery policy, pricing, and services. No major operational gaps exist because this server is intentionally read-only and does not need create/update/delete tools.