Hydrate several recent Strava activities

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals that the tool is write-only, processes activities one at a time, and reports every outcome, which is useful. However, it does not mention side effects, idempotency, required permissions, or error behavior, leaving significant 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 just two sentences, front-loaded with the core purpose ('Write-only targeted batch enrichment'). Both sentences add non-redundant information, making it highly efficient and easy to parse.

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?

Given six parameters, no output schema, and no annotations, the description is insufficiently complete. It does not clarify what 'hydrate' actually does, what the outcome reports look like, or the purpose of limit/refresh, making it risky for an agent to invoke confidently.

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 schema has 0% description coverage, so the description must compensate. It adds high-level meaning by distinguishing an 'explicit list' (activityIds) from a 'bounded date/sport window' (startDate, endDate, sports). Yet it does not explain 'limit' or the 'refresh' boolean, which are ambiguous without further context.

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 it is a 'write-only targeted batch enrichment' and explains how to select activities via an explicit list or bounded date/sport window. This distinguishes it from sibling hydrate_strava_activity, which is singular, by emphasizing batch processing and 'several recent' activities.

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 description implies when to use this tool by contrasting 'batch' against the singular hydrate_strava_activity and by offering two selection modes (explicit list vs. date/sport window). However, it does not explicitly name alternatives or state when not to use the tool, so it stops short of a full exclusion set.

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