get_glucose_history

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

Annotations already declare readOnlyHint=true. The description adds default behavior (24 hours) and return format, but no additional behavioral traits beyond the schema and annotations. Adequate.

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?

Four sentences, each serving a purpose: purpose, return format, use cases, default. No wasted words, front-loaded with key information. Excellent.

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 a single optional parameter, readOnlyHint, and no output schema, the description covers the essential aspects (purpose, return, default, use cases). Missing mention of pagination or limits, but schema covers hours constraints. Good.

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 100% coverage with detailed parameter description. The description only mentions 'default retrieves 24 hours', which adds minimal value beyond the schema. Baseline 3.

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 it retrieves historical glucose readings and returns timestamped values, distinguishing it from sibling tools like get_current_glucose. However, it does not explicitly name alternatives, so it's clear but not top tier.

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?

The description provides use cases (reviewing past levels, identifying patterns, overnight values), implying when to use it, but lacks explicit exclusions or alternatives. Adequate but not explicit.

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