Get full details for a single program by slug. Use this after search_programs returned a result and the user wants to know more — full description, schedule, registration timing, contact info.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Program slug from search_programs results (e.g. 'lodi-fc-competitive-soccer'). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states it returns 'full details' without disclosing authentication needs, error handling, or side effects. Minimal behavioral transparency.
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, front-loaded, no redundant information. Every sentence adds value.
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?
Describes return content (full description, schedule, registration timing, contact info) which is adequate given no output schema. Lacks details on error cases or missing programs, but acceptable for a simple retrieval 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 covers 100% of parameter 'slug' with clear description and example. Tool description adds no additional semantic value beyond the schema, meeting baseline.
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 verb 'Get full details' and resource 'single program by slug'. Distinguishes from sibling 'search_programs' by specifying post-search usage.
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 advises using after 'search_programs' results, providing clear context. Does not specify when not to use or list alternatives, but sufficient for typical use.
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.
