get_steps

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'normalized' and 'for the requested number of days,' which provide some behavioral context, but it does not explain what normalization means, how the days are calculated, or any other side effects or constraints. This is minimal and leaves room for ambiguity.

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, clear sentence with no filler. It front-loads the main function (get normalized daily step counts) and includes the key parameter behavior (number of days) without any unnecessary detail.

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 the tool's low complexity (one parameter, no annotations), the description covers the essential purpose and parameter semantics. An output schema exists, so return values need not be described. However, it could briefly clarify 'normalized' or the exact time window, making it complete but not exhaustive.

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 has 0% description coverage for the 'days' parameter, so the description must compensate. It states that step counts are for the requested number of days, which directly explains the semantic of the parameter beyond the enum values. This adds meaning and helps the agent understand what to provide.

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 that the tool retrieves normalized daily step counts for a specified number of days. The verb 'get' and resource 'daily step counts' are specific, and it distinguishes itself from sibling tools that focus on heart rate, sleep, or health summaries.

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 implies usage when step count data is needed, but it does not explicitly state when to use this tool over alternatives like get_health_summary. There is no guidance on exclusions or comparison with siblings, so the usage context is implied rather than explicit.

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