get_all_day_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 states only the action 'Get' without clarifying whether it is read-only, if there are side effects, or how it behaves on errors or missing data. The name implies a read operation but this is not explicit.

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 extremely concise, consisting of one sentence and a parameter format line. No unnecessary information is included, and every word adds value.

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 description is complete for a simple getter in terms of its action and parameter, but it does not describe the output format, data structure, or possible error conditions. Given the simplicity, this is acceptable but leaves some gaps.

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 input schema has a single required parameter 'date' with no description. The description adds the format 'YYYY-MM-DD' but does not explain the semantic meaning (e.g., the specific day for which stress is requested). This is minimal but adequate for a straightforward date parameter.

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 'Get all-day stress data' clearly states the action (get) and the resource (all-day stress data). It is specific enough to distinguish from generic stress queries, though it does not explicitly differentiate from sibling tools like get_stress_data.

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 on when to use this tool versus alternative stress-related tools such as get_stress_data, get_stress_summary, or get_weekly_stress. The description does not mention conditions, fallbacks, or selection criteria.

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