Hydrate one activity from Strava

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

With no annotations provided, the description takes on the burden of disclosing side effects. It explicitly says 'Write-only' and states it 'archives and persists' activity data, making the mutating nature clear. However, it does not mention error behavior, idempotency, or what happens if no match is found, which prevents a higher score.

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 three sentences with the central action front-loaded in 'Write-only targeted enrichment.' Every sentence adds value: purpose, detailed effects, and an alternative. No fluff or redundancy.

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 write operation with no annotations and no output schema, the description covers the main usage context, side effects, and an alternative. It lacks details about the refresh parameter, return value, and failure modes, but the core use case is sufficiently described.

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 description coverage is 0%, so the description must compensate for both parameters. It clarifies that activityId refers to a 'Catence activity/source' rather than a Strava ID, but it says nothing about the optional 'refresh' boolean, which is a notable gap. It partially compensates but is incomplete.

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 the tool's function: 'Write-only targeted enrichment' that 'safely matches exactly one Catence activity/source to Strava, then archives and persists its activity detail, gear assignment, and segment efforts.' This specific verb-resource combination distinguishes it from sibling tools like hydrate_recent_strava_activities (batch) and get_activity_segments (read-only).

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 provides when-not-to-use guidance: 'For a segment/climb request, prefer get_activity_segments, which invokes this prerequisite automatically.' It also implies targeted single-activity usage versus batch hydration via the 'exactly one' phrasing.

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