Hydrate and read an activity’s Strava segments

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

With no annotations, the description carries the full burden and does disclose a key behavioral trait: it automatically hydrates the activity before returning results. However, it omits side effects of hydration, rate limits, possible errors, and whether refresh forces re-hydration, leaving important behavioral gaps.

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 two sentences, front-loaded with the purpose, and the second sentence adds a valuable usage directive. Every word earns its place with no repetition or filler.

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?

There is no output schema and no annotations, so the description should carry more context. It communicates the core workflow and return type ('persisted segment efforts'), but leaves out limit pagination behavior, refresh semantics, and failure cases—making it adequate but not fully complete.

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 0%, so the description must compensate. It indirectly clarifies activityId (the selected activity), but limit and refresh are not explained at all, leaving their semantics and effect ambiguous to the agent.

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 clearly states a specific verb and resource: it hydrates a Strava activity and returns its persisted segment efforts, covering segments, climbs, KOM/PRs, and per-segment analysis. This distinguishes it from sibling tools like hydrate_strava_activity by centering on reading segment data after hydration.

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 gives explicit usage context: 'For a selected activity's segments, climbs, KOM/PRs, or per-segment analysis' and directs the agent to 'Use this before saying segment data is unavailable.' It does not explicitly mention when not to use it or name alternatives, so it falls short of a 5.

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