get_all_day_stress

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

No annotations are provided, so the description carries the full burden. It states only what the tool does, not any behavioral details such as response shape, date range semantics, timezone handling, or how 'all-day' differs from other stress endpoints. The output schema exists but is not referenced in the description.

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 minimal and front-loaded: one clear sentence plus the parameter definition. Every word adds value and there is no redundant text, making it easy for an agent to parse quickly.

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?

The tool is simple with one parameter and an output schema exists, so a lengthy description is unnecessary. However, given the large set of stress-related siblings, some explicit differentiation or usage context would make the definition complete enough for reliable selection.

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%, so the description must compensate for the undocumented 'date' parameter. It does so by specifying the required format 'YYYY-MM-DD.' This is sufficient for the single required parameter, though it does not explain edge cases like timezone interpretation.

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 states a specific verb and resource: 'Get all-day stress data.' This is clear about what the tool returns. However, it does not differentiate it from sibling tools like get_stress_data or get_stress_summary, so an agent must infer the distinction from the name alone.

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 provided about when to use this tool versus alternatives such as get_stress_data, get_stress_summary, or get_weekly_stress. There are no context clues, exclusions, or selection criteria to help an agent choose correctly among similar stress-related tools.

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