hydration

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

No annotations are provided, so the description must fully disclose behavior. It only states what data is returned without explaining access requirements, default date handling, data range limitations, or whether the tool is read-only. This is inadequate for a tool that likely requires authentication and has implicit date behavior.

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 very brief (two phrases) with no extraneous content. However, the conciseness comes at the cost of completeness. A slightly longer description with structured information would be more effective.

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?

Despite having an output schema (not shown), the description fails to complement it. For a tool with one optional parameter and many siblings, the description should clarify expected output format, units, and behavior when no date is specified. The current text provides almost no contextual completeness.

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 0%, and the description adds minimal value. '当日饮水量' implies a daily scope, but does not clarify the expected date format, default value when omitted (likely today), or any constraints. The single parameter's meaning remains ambiguous beyond what the schema's title 'Date' provides.

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 indicates the tool provides daily water intake data, which distinguishes it from siblings focused on other metrics like sleep, steps, or weight. The purpose is specific but the lack of an explicit verb (e.g., 'get' or 'retrieve') slightly reduces clarity.

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 alternatives. With 40+ sibling tools covering various health metrics, the agent receives no context about specific use cases, prerequisites, or exclusions.

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