Get Intensity Minutes

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

The read-only annotation is present, and the description adds that it returns weekly totals and a goal, giving insight into the output. No side effects or hidden behavior are mentioned, but none are expected for a read-only getter.

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, concise sentence that covers the essential functionality without fluff. It is well-structured and easy to parse.

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 there is no output schema, the description provides a reasonable outline of the response (intensity minutes, weekly totals, goal). It lacks specifics like units or formatting, but for a simple getter this is sufficient.

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 schema already fully describes both parameters (date and endDate) with their roles and formats. The description repeats this relationship but does not add new parameter information, so it meets the baseline without extra depth.

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 retrieves intensity minutes (moderate and vigorous) for a date or date range, and includes weekly totals and goal. This is a specific action on a specific resource, distinguishing it from siblings like get_steps or get_heart_rate.

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 explains the primary use case: fetching intensity minutes for a single date or a range when endDate is provided. It does not explicitly mention alternatives, but the context makes it obvious when to use this over similar getters, so it's clear enough.

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