query_metric_series

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

No annotations are present, so the description carries full burden for behavioral disclosure. It mentions no behavioral traits such as read-only nature, authentication requirements, rate limits, or data aggregation behavior. This is a critical omission.

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 under-specified and fails to earn its place. It conveys no useful information beyond the name, which is already present in the tool name itself.

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 complexity (5 parameters, 3 enums, no output schema), the description is completely inadequate. It provides no context on return values, date formatting, or how aggregation interacts with granularity.

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 input schema has 0% description coverage, and the description adds no parameter explanations. Parameters like start_date format, granularity meaning, and aggregation options are left unspecified, making correct invocation guesswork.

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 'Query metric series' is a tautology that merely restates the tool name. It fails to specify that the tool retrieves time-series health metrics like steps, distance, or calories, nor does it differentiate from sibling tools like query_heart_rate or query_sleep.

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?

No guidance is provided on when to use this tool versus alternatives. With sibling tools dedicated to specific metrics, the description should clarify that this tool handles generic metric series and should be used when the desired metric is not covered by a specialized tool.

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