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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful method context by naming Mifflin-St Jeor and TDEE, but it does not explain how the optional activity parameter affects output or what the calculation returns.

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 very short and front-loaded, with no wasted clauses. But its brevity comes at the cost of under-specification for a five-parameter calculator, so it is concise without being appropriately sized for the tool's complexity.

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 five parameters, 0% schema description coverage, an optional activity enum, and no output schema, the description needs to carry more explanatory burden. It names the formula but leaves required inputs, optional activity behavior, and return semantics unexplained.

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% and there are five parameters, yet the description explains none of them. It does not clarify weightKg, heightCm, ageYears, sex, or the optional activity enum, so parameter semantics must be inferred entirely from field names and enums.

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 identifies BMR/calorie calculation and names the Mifflin-St Jeor formula plus TDEE, which is more specific than the tool name alone. However, it does not explicitly state the verb or clarify whether it returns BMR only or also TDEE, and it does not distinguish itself from sibling converters_tdee.

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 guidance is provided. The mention of TDEE could overlap with the sibling converters_tdee, but the description never says when to use this tool instead of that one, nor does it explain required inputs or prerequisites.

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