stress

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states what data is returned (avg/max/min) but does not mention whether the tool is read-only, requires authentication, handles missing dates, or has side effects. This is a significant gap for a data-retrieval tool.

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 short (one line) and states the core purpose efficiently. However, it is underspecified; important details are missing. It earns a middle score because it is not verbose but lacks completeness.

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 (which may clarify return values), the description fails to explain parameter behavior, usage context, or differentiation from sibling tools. For a simple one-parameter tool, the description should at least cover the date parameter and typical use case.

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 single parameter 'date' has 0% schema description coverage, and the tool description does not explain its format, default behavior (null probably means today), or whether it is required. The description adds no semantic value beyond the parameter name.

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 tool as retrieving daily stress score (average, max, min). It specifies the resource (stress score) and the temporal scope (daily). However, it lacks an explicit verb like 'get' or 'retrieve', and does not distinguish from similar sibling tools like 'get_weekly_stress'.

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 alternatives. There is no mention of context, prerequisites, or exclusions. Sibling tools such as 'get_weekly_stress' or 'user_summary' are not referenced, 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.