get_stats_and_body

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful detail that this is an aggregation that internally delegates to a body-composition service, hinting at composite/possibly heavier behavior, but it omits any error behavior, latency, or partial-failure notes.

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?

A single compact sentence with no padding, front-loading the merge behavior. It is efficient, though the internal-service jargon slightly reduces readability over plain resource language.

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 should at least sketch the merged return shape, and it only gestures at it via internal block names. For a composite/aggregating read tool, the missing return-value and merge-semantics detail is a real gap.

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% and the single 'cdate' parameter is fully documented in the schema, so the baseline is 3. The description adds no syntax or format meaning beyond what the schema already provides.

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 conveys that this returns a composite of user summary stats plus the body-composition 'totalAverage' block, but it does so through internal references ('merges getUserSummary', 'delegating to getBodyComposition') rather than stating the user-facing resource. An agent unfamiliar with those sibling endpoints cannot confidently tell what data comes back, and it isn't clearly distinguished from get_stats, get_daily_stats, or get_user_summary.

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?

There is no when-to-use guidance at all. With siblings like get_stats, get_daily_stats, get_user_summary, and get_body_composition, the definition never says when the composite call is preferable to calling those individually, nor any exclusions or prerequisites.

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