get_daily_stress

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

Discloses critical behavioral traits beyond annotations: ranges over 28 days are automatically chunked, Garmin returns a 400 error when end - start > 27, and a reversed range throws GarminError before any request. Also details the exact response shape, which is valuable given no output schema.

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?

Front-loaded with purpose, then endpoint and response shape, then error/chunking behavior. Dense but every sentence adds value; could be slightly improved with bullet points, but no wasted words.

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?

Complete for a read-only tool with no output schema: it explains the response structure, error conditions, and chunking behavior. Annotations cover safety (readOnlyHint), and the description fills in operational details.

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 coverage is 100%, so baseline is 3, but the description adds meaning: start must be before end (reversed range throws), and ranges longer than 28 days are chunked into 28-day windows. These are important parameter-order and range semantics not captured in the schema.

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?

States a specific verb (get) and resource (daily stress level and time at each stress level) over a date range, with clear per-day output fields. It implies daily granularity, distinguishing it from weekly or all-day siblings, but does not explicitly name those alternatives.

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?

Provides implicit usage context (date range, 28-day chunking) but offers no explicit guidance on when to use this tool versus siblings like get_all_day_stress, get_stress_data, or get_weekly_stress. No exclusions or alternatives are stated.

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