medical.bsa

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds substantial behavioral detail beyond annotations: the exact formulas, HALF_EVEN rounding to 4 decimals, float64 handling of non-integer exponents, and a unit pitfall warning.

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 front-loaded with the core purpose and then efficiently covers inputs, output rounding, method formulas, a use case, and a critical caveat. Every sentence adds useful information without repetition.

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?

The tool has an output schema, so return structure need not be explained, and annotations already cover safety/idempotency. The description supplies everything needed to call it correctly: units, input types, method selection, rounding behavior, and a dangerous unit-mistake warning.

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 parameter meaning, and it does. It documents height_cm and weight_kg as Decimal strings in cm/kg, method default dubois, and the mosteller alternative with its formula.

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 states a specific verb and resource: it calculates body surface area (BSA) in m². It makes the tool immediately distinguishable from relatives like medical.bmi or medical.dose_weight_based by naming the exact calculation and units.

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?

It gives a clear clinical use case, anticancer drug dose calculation, so the agent knows the intended context. It does not explicitly name when-not-to-use cases or alternative sibling tools, but the context is still clear.

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