get_body_battery_stress

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

No annotations are present, so the description carries the full burden. It only states the day scope and that it is a summary; it does not disclose default/null-day behavior, timezone handling, read-only nature, or data availability.

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 compact sentence with no filler. The core metric and date format are front-loaded, making it easy to parse.

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 no annotations and no output schema, the description is too thin for an agent to confidently invoke the tool. It covers purpose and date format but omits the meaning of the optional/nullable day parameter and when to prefer this tool over closely related siblings.

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?

The description adds the YYYY-MM-DD format for the day parameter, which the input schema lacks. However, it does not explain what null or omitted day means, leaving a meaningful ambiguity given the schema's default of null.

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 identifies the resource (Body Battery + stress) and the scope (a single day, formatted YYYY-MM-DD). The combined metric differentiates it from siblings like get_daily_stress and get_body_battery, though it lacks an explicit verb such as 'Get'.

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?

The description implies a daily summary use case but gives no explicit guidance on when to select this tool over get_body_battery, get_daily_stress, or get_body_battery_stress_history. No alternatives or exclusions are mentioned.

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