CGM daily summary

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

No annotations are provided, so the description carries full burden. It states the returned stats but omits behavioral traits such as read-only nature, potential cost, or data freshness. For a read operation, it should explicitly note no side effects.

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 a single sentence that efficiently lists outputs in parentheses. It is front-loaded but could benefit from bullet points for readability. Minor structure improvement possible but overall concise.

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 lacks completeness: it does not explain the effect of the 'hours' parameter on the returned data, nor describe the output format. With no output schema, more detail is needed for agent invocation.

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% with a single parameter 'hours'. The description does not add meaning beyond the schema; it mentions 'daily' but doesn't clarify how hours >24 affects the summary (e.g., per-day or overall aggregation). Baseline 3 is appropriate.

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 returns daily glucose stats with specific metrics like mean, median, min/max, etc., and distinguishes from siblings like cgm_glucose_now and cgm_time_in_range by focusing on a comprehensive summary.

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 no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It simply lists outputs without context.

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