get_body_measurements

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

No annotations provided, so description must cover behavior. Mentions pagination and content, but lacks details on ordering (chronological?), data freshness, empty results, authentication, or performance implications. Under-discloses for a tool with no 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?

One sentence, 14 words. Front-loaded with key info (get, paginated list, types). No fluff, efficiently conveys purpose.

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?

Missing details on sorting, date range behavior (despite 'over time'), pagination defaults, and output format. For a tool with two parameters and no output schema, the description is too terse to fully prepare the agent.

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 coverage is 0% with no parameter descriptions. The description adds zero information about parameters page and pageSize (defaults, ranges, behavior). Despite describing the tool as paginated, it fails to explain how parameters control pagination.

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?

Description clearly states verb 'Get', resource 'body measurements', and key attributes: paginated, over time, includes types like weight and body fat. Distinguishes from siblings like get_body_measurement_by_date (single date) and upsert_body_measurement (modify).

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 explicit guidance on when to use this tool vs alternatives (e.g., get_body_measurement_by_date for a single date, upsert_body_measurement for writing). The description implies list retrieval but does not set usage boundaries.

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