접종 시기 백신 조회

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of disclosure. It accurately states the tool returns reference information and is not a diagnosis, adding a valuable safety caveat. However, it does not describe response format or any potential pitfalls like missing parameters.

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?

The description is two concise sentences, each earning its place: one for functionality and one for the medical disclaimer. There is no redundancy or filler.

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 tool with optional parameters and no output schema, the description conveys the core purpose and essential caveat. However, it lacks guidance on the no-parameter case or precedence if both parameters are supplied, which would make it more complete.

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 already describes both parameters (ageInDays and birthDate) with 100% coverage, including the alternative relationship. The description merely repeats this ('based on age (days) or date of birth') without adding syntax or precedence details beyond the schema.

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 that the tool returns due and upcoming vaccines based on age in days or birth date. This specific verb+resource combination distinguishes it from sibling tools like list_vaccine_schedule or compute_growth_percentile.

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 implies usage when age or birthdate is known, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. It only offers a medical disclaimer about consulting a pediatrician.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.