strava_sync_activities

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

The annotations are all false, so they already signal that this is not read-only, not idempotent, and not destructive. The description adds that the effect lands in a 'local ignored activity cache,' which is useful side-effect context. However, it does not disclose whether repeated calls overwrite or append, whether Strava rate limits or pagination are consumed, or what happens to existing cached entries.

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?

One concise sentence with no filler; the key action and destination are front-loaded. The short length is a virtue even though additional behavioral context would be welcome.

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?

With no output schema and only sparse annotations, the description carries a heavy burden, but it does not explain return values, cache-update semantics, or how this differs in use from strava_export_activities or strava_cache_status. An agent can call it with correct parameters thanks to the schema, but cannot predict the result or side effects. The missing behavioral and usage context makes this incomplete for a sync tool.

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 100%, so the input schema already fully documents 'after', 'before', and 'maxPages'. The description adds no parameter-specific details beyond the word 'bounded', which weakly aligns with the after/before bounds. A baseline of 3 is appropriate because the schema does the heavy lifting.

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 names a specific verb ('Fetch'), a bounded resource ('Strava activity history'), and a destination ('local ignored activity cache'). This clearly differentiates it from sibling read tools like strava_recent_activities and strava_activity_detail, which fetch data back to the agent rather than writing into a cache. The qualifier 'ignored' is slightly jargon-heavy but does not obscure the core action.

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 gives no explicit when-to-use or when-not-to-use guidance, and it names none of the 15 sibling tools as alternatives. The cache-writing phrasing implies an internal sync operation, but with so many nearby Strava tools an agent must guess whether this is a prerequisite or a user-facing query. There is no stated exclusion or routing rule.

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