calculate_pediatric_dose

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

No annotations provided, so description must carry burden. It focuses on output contract (structuredContent) but omits behavioral traits like read-only nature, authentication needs, or side effects. Does not disclose that this is a computation, not a database lookup.

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 purpose. The agent contract adds necessary guidance but is concise. No wasted words.

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?

Despite having an output schema, description lacks detail on input constraints, method selection criteria, and result interpretation. For a tool with 8 parameters and 30+ siblings, more context is needed for correct tool selection and use.

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 only 25% (only locale and output_format described). Description mentions method options but does not clarify how adult_dose, child_weight_kg, child_age_years, child_bsa relate to methods. Fails to compensate for low schema coverage.

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 the tool calculates pediatric dose from adult dose using weight, age, or BSA method. However, it does not explicitly distinguish from sibling tools like calculate_dose_by_weight or calculate_dose_by_bsa, which may cause confusion.

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?

No guidance on when to use this tool versus alternatives (e.g., calculate_dose_by_weight, calculate_dose_by_bsa). The agent contract only addresses output handling, not usage context.

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