tdee_calc

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does reveal the $0.001 USDC cost via x402, which is useful, but it omits core behavioral traits like required inputs, whether it is a read-only computation, or what output will be returned.

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 short and not overly verbose, but the leading phrase simply restates the tool name, and the remaining content is thin. It is concise yet under-specified rather than effectively front-loaded with purpose.

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?

Given the absence of annotations, lack of output schema, and a generic parameters object, the description is severely incomplete. It fails to explain what TDEE calculation requires, how to structure the params object, or what the agent should expect in return, especially for a tool that charges a fee.

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% since the only property is 'params', even though its description is generic ('Tool parameters as JSON object'). With high schema coverage, the baseline is 3, and the description adds no parameter-level meaning beyond that.

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 repeats the tool name 'tdee calc' and labels it a 'Health & Fitness tool', but never states that it calculates Total Daily Energy Expenditure or performs any specific action. It lacks a verb+resource structure and does not distinguish it from sibling calculators like bmr_calc or calorie_burn.

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 guidance is given on when to use this tool versus related health/fitness calculators. The category label and cost note do not help an agent decide between tdee_calc and alternatives such as macro_calc or body_fat_calc.

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