medical.dose_weight_based

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

Goes well beyond the readOnly/idempotent annotations by disclosing the capping side effect (returns capped=true), the exact rounding regime (4-dp HALF_EVEN, trailing zeros stripped), and the critical caveat that unit is display-only with no conversion — a real correctness hazard the agent would otherwise get wrong.

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?

Front-loaded with purpose and formula, then input/output contract, then the unit-consistency warning. Every clause carries new information — no restatement of the name or schema types.

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?

With an output schema present the description need not enumerate return fields, yet it still specifies the numeric formatting and the capped flag. Combined with annotations covering safety and idempotency, an agent has everything needed to call this correctly.

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 carry the load, and it does: weight_kg and dose_per_kg are constrained to Decimal strings >= 0, max_dose is optional and triggers clamping, and unit is explicitly presentation-only. All four parameters get meaning that the bare schema (string/anyOf, default "mg") does not provide.

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?

States a specific verb and resource (weight-based drug dose calculation) and immediately gives the exact formula dose = weight_kg * dose_per_kg, which pins the tool apart from the other medical.* calculators (bmi, bsa, egfr) in one sentence.

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?

Explains the operational condition clearly: supply max_dose to cap the result, and never mix different units between dose_per_kg and max_dose. It stops short of naming an alternative tool or stating when not to use weight-based dosing, but for a single-purpose calculator the invocation context is unambiguous.

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