Calculate recommended daily water intake.
| Name | Required | Description | Default |
|---|---|---|---|
| weight_kg | Yes | Weight in kilograms | |
| activity_level | No | Activity level: low, moderate, high | moderate |
| Name | Required | Description | Default |
|---|---|---|---|
| weight_kg | Yes | ||
| glasses_250ml | Yes | ||
| activity_level | Yes | ||
| recommended_ml | Yes | ||
| recommended_liters | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It only says 'Calculate recommended' without specifying the formula, assumptions (e.g., weight-based guidelines), or units of output. The activity level parameter's effect is not explained.
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 a single sentence that directly conveys the purpose without any extraneous information. It is optimally concise.
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 tool is simple and has an output schema (assumed to document returns), the description lacks key context about the calculation logic (e.g., formula based on weight and activity level). Adequate but has gaps.
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%, so the schema already documents both parameters. The description adds no additional meaning beyond what is in the schema. Baseline score of 3 is appropriate.
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 'Calculate recommended daily water intake,' which is a specific verb+resource combination. Among siblings like calculate_bmi or ideal_weight, this tool is uniquely about water intake.
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 versus alternatives. For instance, if activity level is relevant, no mention of context like exercise or climate. No exclusions or comparisons provided.
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.
