get_activities_for_date

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description must add behavioral context instead, and it does not. It discloses no return shape, no rate limits, no scoping behaviour — only an internal routing detail about the server path that has no bearing on how the agent should call or interpret the 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 text is short, but brevity alone is not conciseness when the one sentence present does not serve the caller. The sentence begins with 'despite the name', which leads with a disclaimer rather than a purpose, and the implementation detail about the path does not earn its place in an agent-facing description.

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 single-parameter read tool with no output schema and 100% parameter coverage, the description still needs to convey what is returned for a date, and it fails to do so. The annotations cover safety, but the core question — activities or heart rates? — is left unresolved and is in fact muddied further.

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 sole parameter 'fordate' is fully documented as a YYYY-MM-DD UTC calendar date in the schema, so the baseline of 3 applies. The description adds nothing about the parameter, but per the scoring rule the schema carries this dimension.

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 never states what the tool does. Instead it tells the agent that the underlying path is '/mobile-gateway/heartRate/...' and not an activities-service path, which directly undermines the tool's name (get_activities_for_date) rather than clarifying it. An agent reading only this text cannot determine whether the tool returns activities or heart-rate data for the given date.

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, no conditions, and no routing to alternatives such as get_activities_by_date or get_heart_rates, both of which appear in the sibling list and are obvious candidates. The single sentence offers no selection criteria at all.

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