get_daily_stress

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

With no annotations, the description should disclose behavioral traits. It does not mention that this is a read-only operation, any authentication needs, rate limits, or potential side effects. The description only indicates retrieval of data but lacks explicit safety or behavior details.

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 purpose sentence and two parameter lines. No extraneous information. Front-loaded with the most important information.

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?

Given the tool's simplicity (two optional date parameters, no nested objects) and the presence of an output schema, the description adequately covers the retrieval purpose. It lacks broader context like data scope or use cases, but is reasonably complete for a straightforward getter.

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. It adds value by specifying the YYYY-MM-DD format and default values for both start_date and end_date, which is not present in the schema. However, it could include more detail such as allowed date ranges or timezone handling.

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 states the tool gets 'daily stress levels' and specifies the exact sub-components ('stress high, recovery high, day summary'), providing a specific verb-resource pair that distinguishes it from sibling tools like get_daily_activity or get_daily_sleep.

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 versus alternatives, no prerequisites, and no mention of when not to use it. Only defaults for date parameters are provided.

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