Check Zepp cloud connection status, including user ID, session origin (token cache or fresh login), and workout count.
Check the Zepp cloud connection: user id, whether the session came from the token cache or a fresh login, and how many workouts are on record.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It explains what state information is returned but does not explicitly state whether the tool performs network I/O, may trigger a fresh login, or is strictly read-only. The mention of 'token cache or a fresh login' raises ambiguity about 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?
A single front-loaded sentence that states the action and lists the exact outputs. No filler, no repetition, and every phrase adds meaning, making it highly scannable for an agent.
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 zero-parameter, low-complexity status tool without an output schema, the description covers the main return values. It lacks an explicit return shape, but the named fields (user id, session source, workout count) are sufficient for an agent to understand the result.
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?
The tool has zero parameters and schema coverage is trivially 100%, so a baseline of 4 applies. The description adds no parameter details because there are none to document, which is appropriate.
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 opens with a specific verb and resource ('Check the Zepp cloud connection') and enumerates the exact data items it returns: user id, session source (token cache vs fresh login), and workout count. This clearly distinguishes it from sibling tools that handle workouts, devices, and metrics.
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 when to use it: when you need to verify the Zepp cloud connection or see session status. However, it does not explicitly name alternatives or state conditions for when not to use this tool versus a sibling, leaving the routing implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.