calculate_hydration

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

No annotations provided, so description must fully disclose behavior. It describes a health recommendation tool but omits important caveats (e.g., not medical advice) and contradicts the schema by specifying 'temperature °C' when the schema uses a 'climate' enum. This mismatch undermines transparency.

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?

Three sentences covering purpose, usage, inputs, and output are efficient, but the inaccurate parameter descriptions (temperature, hours) and lack of structure (e.g., no bullet points) reduce effectiveness.

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 tool's health context and existence of an output schema, the description fails to mention assumptions, limitations, or that results are estimates. The parameter mismatch also indicates incomplete understanding. For a tool with 3 parameters and output schema, the description should be fully accurate and include behavioral context.

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 coverage is 100%, so baseline is 3. However, the description adds misleading information: 'activity hours' vs schema's minutes, and 'temperature °C' vs climate enum. This detracts from the schema's clarity rather than adding value.

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?

Clearly states the tool computes recommended daily fluid intake for athletes and outdoor workers. However, the description mentions inputs as 'temperature °C' while the schema uses a 'climate' enum, causing confusion. Despite this, the core purpose is well-defined.

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?

Explicitly states usage for athletes and outdoor workers and directs to list_bundles for related 'sante' calculators, providing alternative guidance.

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