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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, side-effect-free computation. The description adds genuine value by naming the Mifflin-St Jeor formula, which lets an agent judge the calculation's validity, but it omits any behavioral detail beyond the annotations, such as units handling 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?

It is a single front-loaded line, which is efficient, but 'client and server side from freedailypro' is branding noise that earns no place in a tool description and consumes roughly a third of the text.

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 5 parameters at 0% schema coverage and no output schema, the description should explain units, the meaning of required vs optional inputs, and what the caller receives back. It covers none of that, leaving the parameterization and return value entirely 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 0% across 5 parameters, so the description must carry the load and it does not. It says nothing about weightKg/heightCm units, the sex enum, age bounds, or that activity is optional and drives the TDEE component; the only hint is the bare mention of 'TDEE'.

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 the resource (a BMR calorie calculator) and names the formula it uses (Mifflin-St Jeor) plus its TDEE output, which is specific enough to know roughly what it computes. However, it never distinguishes itself from close siblings like converters_tdee, calculate_bmi, calculate_ideal_weight, or estimate_body_fat, and mentioning TDEE without routing to the dedicated sibling tool creates ambiguity rather than clarity.

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?

There is no statement of when to use this tool versus the many adjacent calculators, no prerequisites, and no note that the optional activity parameter is what turns the result into a TDEE. The only implicit cue is the word 'TDEE' in the description.

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