vo2max_calc

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

With no annotations, the description must disclose behavior. It indicates the tool is a calculator (non-destructive, read-only) and lists parameters, but does not explain error handling, input validation, or output units. The output schema exists but is not referenced.

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 concise with an efficient structure: a single-line purpose followed by a parameter list. No redundant sentences. Every line contributes useful information, and the purpose is front-loaded.

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 description covers all parameters and their roles, but lacks details on the output format (e.g., VO₂ max units) and potential constraints (e.g., realistic value ranges). Given the output schema exists, the omission is minor but reduces completeness slightly.

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%, but the description compensates fully. Each parameter gets a clear meaning: 'resting_hr' as 'Resting heart rate in bpm', 'method' with defaults ('resting' or 'exercise'), and 'weight' as optional for exercise. This adds value beyond the schema's simple titles.

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 'Estimate VO₂ max using resting heart rate or exercise test', which is a specific verb ('estimate') and resource ('VO₂ max'). It distinguishes itself from sibling health calculators (e.g., bmr_calc, body_fat_calc) by focusing on a unique metric and methodology.

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 provides no guidance on when to use this tool versus alternatives like bmr_calc or tdee_calc. It does not mention prerequisites, preferred use cases, or exclusions. An explicit comparison or context for selection is missing.

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