성장 백분위 계산

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

With no annotations, the description carries the burden and does add useful limitations: it is reference information, not a diagnosis, and is scoped to WHO charts for 0–24 months. However, it does not disclose behavior regarding missing age inputs, output format, or validation, leaving key behavioral aspects unstated.

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 with the core function, followed by a concise disclaimer. No filler or redundant content.

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 six-parameter calculation tool with no output schema or annotations, the description gives the essential purpose and limitations but misses important operational details, such as how age should be specified (birthDate vs ageMonths) and what happens if it is omitted. It is adequate but not fully 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 description partially supports the schema by naming weight/height/head circumference and the 0–24 month age range, which aligns with the 'measure' and 'ageMonths' fields. Schema description coverage is 67%, and the description adds context but does not explain the relationship between birthDate and ageMonths or the meaning of all parameters.

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 states a specific action ('calculates z-score and percentile') for a clear resource (WHO growth charts, 0–24 months) across three measurement types. It distinguishes from sibling vaccine/checkup tools by focusing on growth metrics.

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 communicates that results are reference-only and advises consulting a pediatrician, which gives context, but it does not explicitly state when to choose this tool over other tools or what conditions make it inappropriate. The intended use is implied rather than directly contrasted with alternatives.

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