get_running_summary

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

With no annotations provided, the description carries the full burden. It does not state that the tool is read-only, nor does it describe any behavioral characteristics such as data range, aggregation, or limitations. The 'days' parameter that controls the summary window is not mentioned, leaving the agent uninformed about how the operation behaves.

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 immediately lists the key contents of the summary. It is well-structured and front-loaded with the most important information, with no unnecessary words.

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?

While an output schema exists to cover return values, the description is incomplete given the available context. It does not explain the 'days' parameter, does not distinguish from sibling tools like get_monthly_running_stats, and lacks usage guidance. The tool is simple, but the missing parameter semantics and context leave significant gaps.

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 only parameter 'days' has zero description coverage in the tool description. The schema provides type and default but no semantic meaning. The description fails to explain what 'days' represents or how it affects the summary, offering no value beyond the 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 indicates a running summary with specific metrics (sessions, distance, pace, HR, etc.). The purpose is evident but lacks an explicit verb like 'get' or 'list' in the description itself. It doesn't explicitly distinguish it from siblings like get_monthly_running_stats, but the metric list provides some differentiation.

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. There is no mention of preferred scenarios, prerequisites, or exclusions. The description is purely a noun phrase without any usage context.

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