Get body measurements

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

The readOnlyHint annotation already discloses that this is a safe read operation. The description adds one behavioral detail, 'newest first,' which is useful, but it does not mention pagination behavior or any other side effects. Given the strong annotation coverage, this is adequate but not exceptional.

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 five words long, front-loads the main verb and resource, and includes the most important behavioral modifier. Every word earns its place with no repetition or filler.

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?

For a simple list tool with one optional parameter, a readOnlyHint annotation, and an output schema, the description is mostly complete. The only notable gap is the lack of explanation for the limit parameter, but the schema's name and default provide enough context for an agent to invoke the tool correctly.

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%, and the description does not explain the only parameter, 'limit.' While the name and default value in the schema provide some hint, the description fails to compensate for the low schema coverage by stating how the limit affects results.

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 states a clear verb and resource: 'List body measurements.' It also adds the ordering behavior 'newest first,' making the tool's purpose immediately identifiable. This differentiates it from sibling log_body_metric, which is clearly a write operation.

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 implies usage for reading body measurements through the verb 'list,' and the readOnlyHint annotation reinforces this. However, it does not explicitly mention when not to use it or point to a sibling alternative such as log_body_metric for logging measurements.

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