summarize_workouts

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

With no annotations, the description carries full responsibility for disclosing behavior, but it only states the aggregation operation. It does not mention return format, read-only status, date handling, or side effects, leaving significant behavioral aspects undisclosed.

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 sentence, directly states the action, and contains no redundant words. It is appropriately sized and front-loaded with the verb.

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 no output schema, no annotations, and a very brief description, the tool lacks details on return values, the precise meaning of 'workout volume' (distance, duration, etc.), and date range behavior. This would hinder an agent from correctly invoking the tool without additional context.

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 description adds meaning by mapping 'sport' to activity_type and 'ISO week' to week, clarifying the group_by parameter. However, it does not explain start_date/end_date formats or semantics. With 0% schema coverage, this partial compensation earns a middle score.

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 ('Summarize') with a clear resource ('workout volume') and grouping dimensions ('by sport or ISO week'). It distinguishes itself from siblings like query_workouts (which retrieves records) and compare_workout_periods (which compares periods) by indicating it provides an aggregated 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?

No guidance is provided on when to use this tool versus alternatives such as query_workouts or get_daily_summary. The description lacks explicit use cases, prerequisites, or exclusions, leaving selection to inference.

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