upsert_body_measurement

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

No annotations are provided, so the description carries full burden. It mentions 'create or update' but does not specify the behavior when a measurement for the given date already exists (overwrite, merge, or error). No details on data validation, authentication needs, 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 of 9 words, concise and front-loaded. It efficiently conveys the core purpose, though it lacks detail that might be helpful. It does not waste words.

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 the lack of output schema, no behavioral transparency, and no usage guidelines, the description is incomplete. It does not cover what happens on success, error conditions, or the structure of the measurement object. For a tool with a nested object parameter and no output schema, more context is needed.

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 100%, so the schema already describes both parameters. The description adds no additional meaning beyond the schema—it does not elaborate on the measurement object's expected keys or provide examples. Baseline is 3 with no added value.

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 action (create or update) and resource (body measurements for a specific date). It distinguishes from sibling tools like get_body_measurement_by_date (read) and get_body_measurements (list). However, it could be more explicit about the upsert behavior (overwriting vs. merging).

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 provides no guidance on when to use this tool versus alternatives. For instance, it doesn't clarify that this is for adding or updating a single date's measurements, while get_body_measurement_by_date is for retrieval. No exclusions or prerequisites are mentioned.

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