get_activity_workouts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further: no word on what a 'structured workout' contains, whether an activity may have zero workouts, or whether the result is a list or single object. With no output schema, that return-shape gap matters.

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?

One front-loaded sentence with zero filler and no redundancy. It is efficient, though its brevity comes partly from omitting useful detail rather than from precision.

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 tool with one undocumented parameter and no output schema, the description should at least characterize the return value and the identifier. Neither is present, leaving an agent to guess what 'structured workouts' are returned as.

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 0% and the single parameter, activity_id, is undocumented in the schema. The description only implies an activity reference via 'during an activity' — it never says which identifier type is expected or where to obtain it, so it does not compensate for the coverage gap.

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?

States a specific verb ('Get') and resource ('the structured workouts performed during an activity'), which is clearly distinct from sibling get_activity and get_wellness_activities. It stops short of sibling differentiation, and 'structured workouts' is a domain term an agent may not know the shape of.

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?

There is no guidance on when to use this versus get_activity, get_wellness_activities, or search_activities, and no prerequisites or exclusions. Usage is only inferable from the phrase 'during an activity'.

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