Hydrate one activity from Strava

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal that the operation is write-only and that it archives and persists data, which is useful. However, it does not explain idempotency, reversibility, failure behavior, or what the refresh parameter changes, leaving important side-effect details opaque.

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?

Three tightly written sentences, each earning its place. The main purpose and side-effect profile are front-loaded, followed by a routing note and a required prerequisite. There is no redundant or filler content.

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 description covers purpose, main usage, and a prerequisite, which is enough for basic selection and invocation. However, with no output schema and no annotations, an agent cannot determine what the tool returns, how refresh behaves, or what failure modes exist. This is a notable completeness gap for a mutating operation.

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 explain parameters. It tells the agent that athleteId comes from list_athletes, but it does not explicitly define activityId's meaning and leaves the refresh boolean completely unexplained. This is only partial compensation for the empty schema 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 a specific action ('matches exactly one Catence activity/source to Strava, then archives and persists') and clearly names the affected resources: activity detail, gear assignment, and segment efforts. It also distinguishes itself from get_activity_segments by noting that the sibling invokes this tool automatically.

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 explicitly routes segment/climb requests to get_activity_segments, names the prerequisite for athleteId via list_athletes, and clarifies this is a targeted single-activity operation. This gives an agent clear when-to-use and when-to-avoid guidance.

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