get_exercises

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

No annotations are provided, so the description must convey behavior. It discloses the 30-day time constraint and optional parameters. However, it does not describe what happens when there are no exercises, potential errors, or data freshness guarantees. For a simple read tool, this is adequate but not fully transparent.

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?

Two sentences, no unnecessary words. The first sentence defines the core purpose, and the second adds optional functionality. Perfectly concise.

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?

With no output schema, the description should summarize the return format. It only says 'exercise data' without detailing fields. Given the low complexity of a list endpoint, this is acceptable but could be more informative (e.g., 'start time, duration, calories').

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 coverage is 100% with clear descriptions for both parameters. The description adds context by saying 'for deeper analysis', but this largely restates the schema. Baseline 3 is appropriate as the description does not significantly augment 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 states the verb 'Get', the resource 'exercise data from Polar', and the scope 'last 30 days'. It also distinguishes from siblings by mentioning optional detailed samples and training zones, which are specific to this tool among many get_exercise* siblings.

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 that detailed data is optional ('Can include... for deeper analysis'), but does not explicitly state when to use this tool vs alternatives like get_exercise (single) or get_exercise_fit. No when-not-to-use or prerequisites are given.

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