tdee_calc

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

No annotations are provided, so the description must disclose behavior. It states the calculation but does not mention the return format (e.g., calories per day), potential approximations, or any assumptions. For a read-only calculator, this is minimal but incomplete.

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 extremely concise: one main sentence and a clear parameter list. No filler or redundant information. The structure front-loads the purpose and then lists parameters efficiently.

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?

While the description covers parameters well, it does not describe the output (though an output schema exists). It could mention that the result is in kcal/day. For a 5-parameter tool, the description is adequate but not fully self-contained.

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?

The description adds units for weight (kg), height (cm), age (years), and enumerates allowed values for sex and activity, which are absent from the schema (0% coverage). This significantly helps the agent understand parameter constraints beyond types and defaults.

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 clearly states it calculates Total Daily Energy Expenditure (TDEE) based on activity level. The verb 'Calculate' and specific resource 'TDEE' provide clear purpose. However, it does not explicitly distinguish from sibling tools like bmr_calc, though the focus on activity level implies the difference.

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 guidance on when to use this tool versus alternatives like bmr_calc or macro_calc. The description does not specify that TDEE is for maintenance calories or that BMR is for resting state. No alternatives are mentioned.

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