get_body_composition

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: the maximum date range of 92 days, which is not evident from the schema. The verb 'Return' implies a read-only operation, and no side effects are suggested, which is adequate for a simple data retrieval tool.

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 one concise sentence of 12 words, front-loaded with the action and resource. It wastes no words and every element earns its place, including the critical range limit.

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 low complexity (two optional parameters), full schema coverage, and the presence of an output schema, the description is largely complete. It adds the essential 92-day constraint but does not explicitly guide tool selection among siblings, though the name and description already make the use case clear.

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?

The schema already provides 100% coverage for each parameter's format and defaults, so the baseline is 3. The description adds extra meaning by constraining the combined date range to a maximum of 92 days, a relationship between the parameters not present in the schema.

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 uses the specific verb 'Return' and identifies the resource as 'body composition data' with a scoped date range constraint (max 92 days). This clearly distinguishes it from sibling tools like get_latest_body_composition, which targets a single latest measurement, and get_measurements_range, which likely covers other metric types.

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 clear context that this tool is for retrieving body composition data over a date range, and the explicit max 92-day limit is a practical usage constraint. It does not name specific alternatives or exclusions, but the scope is unambiguous for the agent to infer when this tool is appropriate.

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