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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral detail beyond them: results are ordered oldest-first, grouped by date, and default to a 90-day range, plus an auth requirement — meaningful operational context for an agent.

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?

Three tight sentences, front-loaded with the resource and payload, followed by ordering/grouping and defaults. The redundant 'Trainerize:' prefix duplicates the title, but otherwise every sentence carries information.

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?

There is no output schema, so the description correctly assumes responsibility for the return shape, covering ordering and date grouping. Combined with the auth note and default range, an agent has nearly everything needed; only explicit sibling routing is absent.

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 three parameters (client_id, from, to) are already documented with defaults in the schema. The description restates the 90-day default but adds no format or edge-case meaning, so baseline 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?

States a specific verb (get) and resource (body stats) and enumerates the exact entry types returned: body weight, body fat, measurements, calipers. This is clearly a read of logged client metrics, which separates it from the write sibling trainerize_log_body_stats, though that sibling is never named explicitly.

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?

Provides the default date window (last 90 days) and the auth precondition (Cotlet API key with app access), which is useful context, but gives no explicit when-to-use guidance or contrast with trainerize_log_body_stats. Usage is implied rather than stated.

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