Get workouts

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, but the description adds crucial behavioral constraints: the maximum 90-day range and the exclusion of strength-builder workouts. This goes beyond annotation-only information.

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?

Three short, dense sentences. No filler. The most important information (what it does, usage tip, and exclusion) is front-loaded, and every sentence earns its place.

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?

For a simple list tool with no output schema, the description covers all necessary context: what it lists, what to query, the day limit, the exclusion, and the alternative tool. It is complete enough to use without further documentation.

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?

Input schema covers 100% of parameter descriptions, so the baseline is 3. The description adds the meaningful constraint that the date range must be within 90 days, which directly informs how start_date and end_date should be used. This slight addition justifies a 4.

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 states a specific verb ('List') and resource ('workouts') with a clear scope ('in date range'). It distinguishes itself from siblings by explicitly mentioning it excludes strength-builder workouts and points to the alternative tool tp_get_strength_workouts.

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?

Provides explicit usage guidance: 'Query only days needed' and 'Max 90 days', which helps avoid excessive requests. It also tells when NOT to use it (strength-builder workouts) and names the alternative tool.

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