Upcoming events (practices, games, scrimmages, cancellations) for a specific program. Returns next 30 days. Use this to answer 'is there a game this Saturday?' style questions, and to power Add-to-Calendar flows.
| Name | Required | Description | Default |
|---|---|---|---|
| days_ahead | No | ||
| program_slug | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries full burden. It mentions returning next 30 days but does not clarify that the optional days_ahead parameter can extend up to 90 days, creating a minor discrepancy. Missing details on authentication, rate limits, or other behavioral traits.
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 defines what the tool does, second gives use cases. No wasted words, effectively front-loaded with essential information.
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 2 parameters and no output schema, the description covers basic purpose but lacks parameter semantics and behavioral details. The 30-day default vs 90-day maximum is unclear, and there is no info on return format or pagination. Incomplete for a query tool.
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 0% with no parameter descriptions in schema. Description implies program_slug is needed ('for a specific program') but does not explain it. days_ahead is mentioned only indirectly via 'returns next 30 days', not clarifying it controls the lookahead period. Parameters are insufficiently explained.
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?
Description uses specific verb 'returns' and lists event types (practices, games, scrimmages, cancellations) for a specific program. It also clearly defines the timeframe (next 30 days) and provides concrete use cases, distinguishing it from siblings like list_upcoming_events or parent_my_upcoming_events.
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 states when to use: for answering game-related questions and powering Add-to-Calendar flows. This provides clear context, though it does not mention when not to use or offer alternative tools.
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.
