get_workouts

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

No annotations are provided, so the description must convey behavioral traits. It mentions retrieving workout sessions but does not disclose whether it returns all sessions, uses pagination, or is read-only. The date range behavior is implied via schema but not explicitly stated as defaulting to today's date.

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 two sentences with no redundant words. It efficiently states the purpose and use case, making it easy to read.

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?

The description lists the fields returned, which is helpful given no output schema. However, it lacks details on response format, ordering, or any filtering beyond dates. For a relatively simple tool with no output schema, it is adequate but not thorough.

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 100%, so the schema already documents both parameters. The description does not add additional meaning beyond what the schema provides, meriting the baseline score of 3.

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?

Description clearly states it gets workout sessions and lists specific data fields (activity type, duration, etc.), indicating the resource and verb. However, it does not explicitly differentiate from siblings like 'get_activity' or 'get_sessions', which may also return workout-like data.

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 suggests using the tool to analyze exercise patterns, frequency, and training load, which implies when to use it. However, it provides no guidance on when not to use it or alternative tools for similar purposes, such as 'analyze_adherence' or 'get_activity'.

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