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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered. The description adds the formula (Mifflin-St Jeor) and the US-unit convention, which is useful context for interpreting inputs, but says nothing about defaults for the four optional parameters or what the response contains.

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?

A single front-loaded sentence with no filler; every clause (what is estimated, the formula, the unit system) carries information an agent needs.

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 no output schema, the description does not indicate what comes back (e.g. BMR and TDEE values) or how optional parameters are defaulted, which matters for a 6-parameter calculator. It is adequate for invoking the tool but leaves the result shape and optional-parameter behavior unspecified.

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 100%, so the schema already documents every parameter, giving a baseline of 3. The description adds the unit-system constraint ('US units') and the formula context, but does not clarify the activity multiplier semantics beyond the schema's own 1.2 example or the defaults when age/sex/activity are omitted.

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 (estimate) and specific resources (BMR and total daily energy expenditure), plus the formula and unit system, so an agent knows exactly what is computed. It fails to distinguish itself from the near-identical sibling bmr_tdee (and maintenance_calories), which is the main remaining gap.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named. With siblings bmr_tdee, maintenance_calories, and bmi present, an agent has no textual basis for choosing this tool over them.

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