query_workouts

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

With no annotations and a one-word description, the tool's behavioral impact is completely opaque. The agent cannot determine if this is a read-only operation, what data is returned, or any side effects.

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 under-specified rather than concise. A single sentence that adds no value beyond the tool name is not a virtue; it omits critical information the agent needs.

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 5 parameters, 2 required, and no output schema, the description fails to provide enough context for correct invocation. The agent cannot know what response to expect or how to handle errors.

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 description adds no information about parameters like start_date, end_date, activity_types, etc. The agent has to guess their formats, constraints, and meanings from the schema alone, which is insufficient.

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 'Query workouts' is a tautology that merely restates the tool name without specifying what exactly is queried, what filtering capabilities exist, or how it differs from sibling query tools like query_heart_rate or query_sleep.

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 gives no indication of when to use this tool versus alternatives. There is no guidance on prerequisites, expected usage context, or typical scenarios where this tool is appropriate.

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