zepp_list_workouts

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It discloses that results include sport-specific metrics, adding value beyond the schema. However, it does not mention ordering, pagination, or that it returns summaries, leaving some gaps for a read-only list operation.

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 a single, front-loaded sentence with no wasted words. It effectively communicates the core purpose and key detail about metrics, making it highly concise and well-structured.

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 4 optional parameters, the description covers purpose and metric variety, and an output schema exists so return structure is not needed. However, it lacks explicit usage guidance and does not clarify parameter behavior beyond the schema names, leaving modest gaps.

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%, so the description must compensate. It partially addresses the 'sport' parameter by saying 'across all sports' and hinting at sport-specific metrics, but entirely ignores 'limit', 'from_date', and 'to_date'. This is minimal compensation for four undocumented parameters.

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 tool's action ('List workouts') and scope ('across all sports'), with specific detail about sport-specific metrics. This distinguishes it from sibling tools like zepp_workout_detail, which likely retrieves details for a single workout.

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 the tool is for browsing workouts and their metrics, but does not explicitly state when to use it versus alternatives like zepp_workout_detail. Context suggests listing versus detail, but no explicit exclusions or alternative guidance is provided.

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