Retrieve Garmin Connect blood pressure readings for a specific date or date range; if no end date is given, it defaults to the start date.
enddate defaults to startdate
| Name | Required | Description | Default |
|---|---|---|---|
| enddate | No | Calendar date, YYYY-MM-DD (UTC) | |
| startdate | Yes | Calendar date, YYYY-MM-DD (UTC) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already supply readOnlyHint and openWorldHint, so the safety profile is covered. The description adds only the enddate-default behavior and says nothing about what data is returned (systolic/diastolic, per-reading vs aggregated), the granularity, or how ranges behave. Minimal value beyond annotations.
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 single sentence is short and has zero filler, but it is under-specified rather than effectively concise: a tool definition needs to earn its place by conveying purpose, and here the only sentence is a minor parameter note.
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?
With no output schema and two date parameters, the description should at minimum say what is retrieved and over what period. Instead it omits the tool's purpose entirely, leaving the agent dependent on the name alone.
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 100%, so the format (YYYY-MM-DD UTC) is already fully documented, giving a baseline of 3. The description does add one genuine piece of information not in the schema — that enddate defaults to startdate — but it addresses only one of the two parameters and no other semantics.
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 never states what the tool does. Its entire content is a parameter-default note ('enddate defaults to startdate'), which tells an agent nothing about retrieving blood pressure readings. The verb/resource is only inferable from the tool name, so the description itself is effectively missing.
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 tool versus alternatives such as get_heart_rates, get_daily_stats, or set_blood_pressure. No context, no exclusions, nothing to distinguish it from the many sibling 'get_*' data tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.