fitbit_get_azm

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

No annotations provided, but description covers caching, auto-sync, live parameter behavior, and return format. Missing auth or rate limit info, but adequate for a read-only metric tool.

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?

Well-structured with paragraphs and bullet points. Slightly verbose but every sentence adds value. Could tighten the description slightly.

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?

Output schema exists (context signal), and description covers purpose, parameters, caching, return format, and sibling differentiation. No gaps identified.

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 0%, but description fully explains each parameter: start_date (format and default), end_date (default today), live (bypass cache). Adds meaning beyond bare 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?

The description clearly states it retrieves daily Active Zone Minutes, the headline cardio metric. It defines AZM, explains double counting, and distinguishes from fitbit_get_activity's active_minutes.

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?

Explains caching behavior and how to bypass with live=True. Contrasts with fitbit_get_activity for intensity vs. wall-clock minutes. Could explicitly state when not to use, but provides sufficient context.

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