CGM connection status

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

No annotations provided; description adequately lists output fields but does not state that the tool is read-only or free of side effects. For a status tool, this is acceptable but could be more explicit.

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?

Two concise sentences front-loading key information. Every sentence adds value with zero redundancy.

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 zero parameters and no output schema, description covers return values comprehensively. Could briefly note safe/read-only nature, but overall adequate for a status tool.

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?

No parameters in input schema; description adds value by detailing expected output fields (provider, reason, credentials, mock/live, env, region). Baseline 4 applies as no parameters to explain.

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 specifies the tool reports active CGM provider (Dexcom/Libre), selection reason, credential presence, mock/live data, and environment details. This clearly distinguishes it from siblings like cgm_glucose_now or cgm_libre_login.

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?

Description implies usage for checking connection status, but no explicit guidance on when to use vs siblings or prerequisites. Context from sibling names suggests it's a diagnostic tool, but no direct guidance.

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