wellness_activity_summaries

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

No annotations are provided, so the description carries the full behavioral burden. It adds the useful default of the last 7 days, but does not disclose what 'wellness activity' comprises, whether the call is read-only, or what the response shape looks like.

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 two short sentences with no filler, and the default range is front-loaded alongside the core purpose. It is appropriately sized and structurally efficient.

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?

With no annotations, no output schema, and two undocumented parameters, the description is too sparse for correct invocation. It omits what the summary contains, the expected date format, and how it differs from the many sibling summary tools.

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%, so start_date and end_date are undocumented in the schema. The description only implies a date range through 'Standard: letzte 7 Tage' and gives no format, boundary, or timezone semantics for either parameter.

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 resource ('Wellness-Aktivitätsübersicht pro Tag') with a per-day granularity, but 'wellness activity' is vague and does not distinguish this tool from siblings such as daily_summaries, sleep_summaries, hrv_summaries, body_battery, or stress. An agent can infer a summary tool but not exactly which wellness data it returns compared with those alternatives.

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 only usage-related information is the default time range ('Standard: letzte 7 Tage'). There is no guidance on when to choose this tool over siblings like daily_summaries or activity_details, and no exclusions or prerequisites are mentioned.

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