List upcoming family events in Lodi, CA — open houses, workshops, community days, storytimes, sports clinics. Different from search_programs (ongoing classes) — these are single-day or short-window events.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max events to return (1-30). Default 10. | |
| category | No | Filter by event category: workshop, open_house, community, showcase, fundraiser, camp_session, storytime, sports_clinic. |
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 discloses the tool lists events and mentions filter availability, but does not specify read-only nature, ordering, pagination, or any safety/reversibility aspects. Minimal behavioral insight.
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 unnecessary words. Front-loaded with the main purpose and includes a crucial sibling distinction. Highly efficient.
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?
For a simple list tool with 2 optional parameters and no output schema, the description covers the domain, scope, and example categories. Minor gap: default limit and ordering (likely chronological) are not mentioned, but overall it is 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 coverage is 100% with descriptions for both `limit` and `category`. The description does not add significant meaning beyond the schema; it mentions event types but not parameter-specific details. 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?
Clearly states the tool lists upcoming family events in Lodi, CA, with specific examples (open houses, workshops, etc.). Explicitly distinguishes from sibling tool `search_programs` by noting these are single-day or short-window events, not ongoing classes.
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?
Provides a clear distinction from `search_programs`, indicating when to use this tool versus that alternative. However, no explicit when-not-to-use or other exclusions beyond that single comparison.
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 clearly grouped by prefix (admin_, daycare_, org_, parent_) and within each group have distinct, non-overlapping purposes. For example, parent_add_kid vs parent_remove_kid are unambiguous.
All tools follow a consistent snake_case pattern with role prefix and action_noun structure. Minor exceptions like 'nearby_programs' are standalone and do not disrupt the overall consistency.
With 72 tools, this is far beyond the typical well-scoped range of 3-15. While the tools cover multiple user roles, the count is excessive and likely overwhelming for an agent, falling into the 'too many' category.
The tool set covers most core workflows for parents, orgs, and admins, but notable gaps exist: there is no tool to create a program or daycare, and admin tools for approving pending claims or discoveries are missing, leaving dead ends.
