detect_episodes

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

No annotations are provided, so the description carries the full burden. It explains time window mechanics and the optional data parameter for persistence layer integration, but does not disclose the return format or explicitly state that it is a read-only operation. While not contradicting any annotations, the description provides only partial behavioral context.

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 well-structured: a one-line purpose, a clearly labeled Args section, and concise examples. Every sentence adds value, with no redundant or filler text.

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?

Covers all parameters and provides usage examples, but lacks an explicit description of the return value. Since there is no output schema, the description should state what the tool returns (e.g., list of episodes). Additional guidance on when to use Dexcom API versus provided data would improve completeness, but the description is mostly thorough.

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%, but the description thoroughly documents all six parameters, including defaults, ranges, and the schema for the data parameter. The examples demonstrate parameter combinations clearly, fully compensating for the lack of schema descriptions.

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?

Description clearly states 'Detect hypoglycemic and hyperglycemic episodes' with a specific verb and resource. It is distinct from siblings like get_episode_details, which retrieves details about episodes. The examples further reinforce the purpose.

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?

Examples show common usage patterns (e.g., minutes=180, start_minutes/end_minutes), implying when to use the tool, but there is no explicit comparison to alternative tools or exclusions. The description does not state when to use this tool versus get_episode_details or check_alerts.

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