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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered; the description adds nothing beyond that. It omits behaviorally important details: which TDEE formula is used, what the returned number represents (kcal/day), and what activity level is assumed when the optional 'activity' parameter is omitted.

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 short sentence, so it is not bloated, but a meaningful share of its words ('client and server side from freedailypro') convey nothing actionable to an agent. There is no front-loaded statement of inputs or output.

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?

For a five-parameter tool with zero schema documentation and no output schema, the description should cover units, the activity default, and the expected result. None of that is present, leaving the agent to guess at invocation details.

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 five parameters, so the description carries the full burden and does not compensate at all. It never mentions units (kg vs lb, cm vs inches), the male/female enum, or the default behavior of the optional 'activity' enum.

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 names the resource (TDEE / calorie expenditure) but the phrasing 'client and server side from freedailypro' is opaque vendor noise rather than a clarifying verb. It does not distinguish this tool from nearby siblings such as calculate_bmr, calculate_bmi, or calculate_ideal_weight, which an agent could easily confuse with it.

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 other calorie/body-metric calculators in the sibling list. No prerequisites, no mention that it requires the four biometric inputs, and no guidance on when BMR alone would suffice instead.

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