get_stress_data

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Get stress levels throughout the day', omitting details like data source, aggregation method, units, or whether results are in real-time or historical. This is insufficient for safe invocation.

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?

Extremely concise: two sentences covering purpose and parameter format. No redundant information, well front-loaded.

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 the presence of an output schema, the description does not explain what stress levels contain (e.g., scores, timestamps). Given the tool's context among many health data endpoints, this omission leaves the agent guessing about return format.

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 parameter 'date' has schema type 'string' with title 'Date'. The description adds the format constraint 'YYYY-MM-DD', which is useful but minimal. With 0% schema description coverage, the description provides the sole semantic context for the parameter, but it is basic.

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 retrieves 'stress levels throughout the day', which distinguishes it from sibling tools like get_heart_rates or get_hrv_data. However, it lacks explicit mention of the date parameter in the main description, relying on the Args section.

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 over alternatives such as get_hrv_data or get_body_battery. The description does not indicate prerequisites or context, leaving the agent without decision support.

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