activity

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 adds that the response is a Garmin summary DTO, but it does not disclose error behavior, authentication needs, or how much detail 'full' actually includes.

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 efficient sentence with no filler. It is front-loaded with the core purpose, though the parenthetical 'Garmin's summary DTO' is somewhat redundant with the earlier 'Garmin detail'.

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 output schema and undocumented parameter semantics, the description is too thin to fully guide invocation. It should at least clarify the activity_id input or the shape of the returned summary DTO.

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?

There is one required parameter, activity_id, with 0% schema description coverage. The description implies a single activity is identified but does not explain the parameter's format, source, or constraints beyond what the bare schema type 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?

States that the tool retrieves full detail for one activity and notes the Garmin summary DTO return type. The singular 'activity' implicitly distinguishes it from the sibling 'activities' list tool, but the verb is not explicit and the differentiation is not spelled out.

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 phrase 'one activity' implies this is for fetching a single known activity rather than listing activities, but there is no explicit when-to-use guidance, no prerequisites, and no direct reference to the 'activities' sibling.

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