Submit a review for a program or daycare. One review per (parent, program). Use parent_update_review to edit afterward.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| kid_id | No | ||
| rating | Yes | ||
| season | No | ||
| daycare_id | No | ||
| program_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose all behavioral traits. It states the core action and the uniqueness constraint but omits details like what happens if a review already exists, required fields for specifying the program/daycare, authentication requirements, or side effects. The description is partially transparent.
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: first states purpose, second gives usage guidance. It is concise and front-loaded with the essential information. However, it could be slightly more structured with parameter hints.
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 6 parameters, no output schema, and no annotations, the description is too brief. It does not cover return values, error scenarios, or detailed parameter usage. It provides the minimum viable information but leaves many details unsaid.
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 description coverage is 0%, so the description must explain parameters. It mentions 'program or daycare' but does not clarify that daycare_id and program_id are optional or that one must be provided. kid_id, season, and text are not explained at all beyond the schema. The description adds little value beyond the parameter names.
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 action ('Submit a review'), the target resource ('program or daycare'), and the constraint ('One review per (parent, program)'). It also distinguishes from the sibling tool 'parent_update_review' by explicitly mentioning it for edits.
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?
The description explicitly tells when to use this tool ('Submit a review') and when to use an alternative ('Use parent_update_review to edit afterward'). The one-review-per-pair constraint also informs usage. This provides clear guidance for an AI agent.
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.
