Estimate calories burned during activities.
| Name | Required | Description | Default |
|---|---|---|---|
| activity | Yes | Activity type | |
| weight_kg | Yes | Body weight in kg | |
| duration_minutes | Yes | Duration in minutes |
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| activity | No | ||
| met_value | No | ||
| weight_kg | No | ||
| calories_burned | No | ||
| duration_minutes | No | ||
| available_activities | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, description carries full burden but only states 'estimate calories burned' – no details on estimation method, limitations, or output structure.
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?
Single sentence is concise but lacks necessary context; score reflects adequate conciseness with insufficient informativeness.
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 an output schema present but no description of return values or edge cases, the description is incomplete for the complexity of estimation.
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 already provides basic descriptions for all 3 parameters (100% coverage), so description adds no extra meaning; baseline 3 applies.
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 uses a specific verb ('estimate') and resource ('calories burned during activities'), clearly distinguishing it from sibling tools like 'calculate_bmr' or 'heart_rate_zones'.
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 on when to use this tool vs alternatives (e.g., 'calculate_bmr'), no prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
