get_profile

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that the payload is static user settings; it says nothing about auth requirements, freshness/caching, or whether zones are user-defined vs. device-derived, which would be genuinely additive.

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 filler, leading immediately with what the resource is before listing its contents. Nothing could be removed without losing 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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile; for a zero-parameter read tool the description is nearly sufficient. It could be stronger by stating the intended workflow position (call this before interpreting activity data), but no essential gap remains.

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 tool takes zero parameters, which is the baseline-4 case. The description's enumeration of fields describes the return payload rather than arguments, but for a no-arg getter there is nothing further to specify.

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 names the resource (user settings/profile) and enumerates its contents — units, time zone, training days, heart-rate zones per sport — so an agent knows exactly what it returns. The 'relevant to interpreting data' framing further distinguishes it from siblings like get_activity or get_training_summary, though it never explicitly contrasts with them.

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?

'Relevant to interpreting data' implies the calling context (fetch this before/while reading units- or timezone-dependent data), which is a useful hint. However, there is no explicit when-to-use statement, no exclusions, and no named alternative among the many siblings.

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