Fetch blood oxygen saturation (SpO2) samples from synced Mi Fitness data by date range, with an optional limit, to support local health trend analysis.
Query blood oxygen saturation samples
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| end_date | Yes | ||
| start_date | Yes |
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, and the description only says 'query', which implies a read-only operation without explicit confirmation. It does not disclose behaviors like return format, pagination, rate limits, or 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 a single sentence, concise and front-loaded. It earns its place by clarifying the resource, though it is sparse on details, which is a separate issue from conciseness.
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?
The description is too minimal for a tool with no output schema and no annotations. It does not explain what 'samples' means, how date filtering works, or what the response contains, making it incomplete for effective use.
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 description provides no information about the parameters (start_date, end_date, limit). With schema description coverage at 0%, the description was expected to compensate but does not, leaving parameter meaning entirely to the schema.
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 queries blood oxygen saturation samples, using a specific verb and resource. It distinguishes from siblings by naming the unique resource (SpO2), though it does not explicitly contrast with other query tools.
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?
No guidance is provided on when to use this tool versus alternatives, such as query_metric_series or other query tools. The description only states the function without any context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.