measurements_list_weight

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only retrieval, but the description does not disclose default limit behavior, available filters, ordering semantics, or any other behavioral traits. It adds little beyond what the tool name already suggests.

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, compact sentence with no filler or redundancy. It is front-loaded and easy to parse, though its extreme brevity means it sacrifices useful behavioral and usage context for conciseness.

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 operation with a fully described input schema and an output schema available, the description may be minimally adequate. However, the lack of annotations and absence of usage guidance leave some context unfilled. The combination of a clear purpose, complete parameter documentation, and output schema keeps it at a viable but not exemplary level.

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 all four parameters are already documented with meaningful descriptions and defaults. The tool description adds no additional parameter context, which is acceptable given the schema's completeness, so the baseline score of 3 applies.

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 combines a specific verb ('List') with a specific resource ('weight measurements'), so an agent can identify the operation and distinguish it from the sibling measurement tools for BMI, height, temperature, and head circumference. It is concise and unambiguous, though it does not elaborate on scope beyond the verb and resource.

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. With siblings like measurements_list_height, measurements_list_bmi, and measurements_list_temperature, an explicit note about choosing this tool for weight data would help. There are no exclusions, prerequisites, or alternative routing hints.

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