Get Recent Activities Summary

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 states the output dimensions but does not explain whether this is read-only, how 'past N days' is bounded, what activity types are included, or how now_ts affects the results.

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, front-loaded sentence with no filler. It delivers the core purpose efficiently, though it is brief enough that some semantic gaps exist in other dimensions.

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?

An output schema exists, so return structure is covered, but the description leaves key invocation context unclear: the role of now_ts, the exact meaning of 'past N days', and how this summary differs from sibling tools. For a tool with two unannotated parameters, this is insufficient.

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 description coverage is 0%, so the description must compensate for both parameters. It only maps 'past N days' to the days parameter; now_ts is entirely unexplained. The description does not fully cover even the days parameter's semantics (e.g., inclusive/exclusive, calendar vs. rolling window).

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 uses a specific verb ('Get a breakdown') and names the exact outputs: activity frequency, total time spent, and last performed dates over the past N days. It is clearly about summarizing recent activities, though it does not explicitly differentiate from the sibling get_recent_workouts or get_training_summary.

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?

There is no guidance about when to use this tool versus siblings such as get_recent_workouts or get_training_summary. No context, prerequisites, or exclusion criteria are provided, so an agent must infer suitability from the name alone.

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