withings_measurements

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

With no annotations, the description must carry the behavioral burden. It does add genuinely useful context: that values are pre-decoded with units baked into keys, and that include_manual=false drops manual entries (a filter behavior). However, it says nothing about pagination, auth requirements, limits, or return shape risk.

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 core purpose and filter behavior are front-loaded and useful, but the long enumeration of 30+ type names bloats the description significantly. The list is helpful but indigestibly long for a tool description.

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 an output schema exists, return value explanation is unnecessary, and the description covers the measurement domains and the key filter. It is largely complete, though the date parameters and pagination behavior remain unaddressed.

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, and it does for `types` (with a full enumerated list and id mapping) and partially for `include_manual`. It provides no format guidance for start_date/end_date, leaving two of four parameters underspecified.

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 what the tool returns ('Body measurements ... grouped by measurement session'), naming the resource and the grouping scope. It does not explicitly differentiate itself from siblings like withings_activity or withings_sleep, which is what keeps it at 4 rather than 5.

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?

It implies when to use the tool (retrieving measurement data) and describes an optional filter, but it never explicitly says when-to-use vs alternatives or provides exclusions. No alternative routing is given despite four sibling tools existing.

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