pregnancy_water_intake

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

No annotations provided, so description carries this burden. It states output is 'a deterministic schedule with explanation, tips, and warnings,' disclosing behavioral traits and safety considerations (warnings). No contradictions.

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 efficiently convey purpose, medical basis, adjustment factors, and output structure. No superfluous 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 calculation tool with 6 params and no output schema, description adequately covers inputs and output format (schedule with explanation, tips, warnings). Could specify units (e.g., ml/day) but sufficient for agent selection.

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%, so description must compensate. It lists factors adjusted for (trimester, activity, climate, morning sickness, breastfeeding) which map to schema parameters, adding medical context that schema lacks.

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 clearly states 'Calculate daily water intake during pregnancy or postpartum.' It names specific medical guidance (IOM 2004, ACOG) and distinguishes from siblings by focusing on pregnancy/postpartum context.

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?

Description implies use for pregnancy/postpartum hydration but does not explicitly state when to use vs. siblings like 'calculate_water_intake' or 'athlete_hydration_plan.' No when-not or exclusion criteria provided.

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