Get Activity Streams

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

Annotations already mark the operation as read-only, idempotent, non-destructive, and open-world. The description adds valuable context that GPS latlng is withheld unless explicit_user_intent is set, and that privacy_mode=raw returns upstream Strava JSON, which goes beyond annotation defaults.

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?

Two sentences with front-loaded action and result; no redundant phrases. The distinction from the sibling is integrated efficiently without extra words.

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?

The combination of high schema coverage, an output schema, and concise description covers purpose, alternatives, and key constraints. While some edge cases (e.g., resolution details) are left to the schema, the essential selection and invocation information is present.

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?

With 86% schema description coverage, the schema documents most parameters. The description enriches this by linking include_gps, privacy_mode, and explicit_user_intent into a cohesive privacy rule, which is not fully captured in individual property descriptions.

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 'Get raw Strava activity streams' and enumerates the specific data types (time, distance, heartrate, cadence, watts, altitude), making the tool's function immediately clear. It also distinguishes from the sibling strava_activity_series by explicitly naming it and describing its alternative purpose.

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?

It explicitly advises 'For agent work prefer strava_activity_series' and explains why (agent-safe-series/v1 with hard point caps and exact stats). This gives the agent clear decision guidance, and also explains GPS access conditions for when to use include_gps/privacy_mode.

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