getActivity

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

With no annotations, the description carries the full burden. 'Get' implies a read-only operation and the description discloses the main response components, but it does not state authentication requirements, error behavior for invalid IDs, or any rate-limit considerations.

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 a single efficient sentence with the core purpose and returned content front-loaded. There is no redundant or wasted text.

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 simple one-parameter read tool with a fully documented schema and no output schema, the description is mostly complete: it identifies the resource and summarizes the return payload. The main omissions are sibling differentiation and how to obtain a valid activityId, which would improve completeness but are not critical to invoking the tool.

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 coverage is 100%, and the single parameter is already documented in the schema as 'Garmin activity id'. The description adds no additional meaning, constraints, or examples beyond what the schema provides, so the baseline of 3 is appropriate.

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 specific verb and resource: get the full detail of one activity. It also lists the returned contents (summary, metadata, splits/laps) and format (JSON), which helps distinguish it from listActivities. However, it does not explicitly differentiate itself from sibling activity tools such as getActivityLaps or getActivityWorkouts.

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?

Usage is implied by 'one activity' and the required activityId, suggesting it is for retrieving a single known activity. But the description gives no explicit when-to-use guidance, no alternatives, and no note that listActivities should be used to discover activity IDs.

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