sync_league

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

With no annotations, the description carries the burden. It discloses automatic week capture and caching recommendation for players, adding useful context. However, it does not mention on whether the sync mutates state, is idempotent, or has rate limits—critical for a sync operation.

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 concise sentences, front-loaded with purpose. Every sentence adds value: purpose, weeks behavior, and include_players guidance. No redundant 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?

An output schema exists, so return values are covered. The description adequately explains main decision points (weeks handling and players). Minor gaps: no mention of 'league_id' semantics, no statement about side effects of syncing, and no prerequisites. Overall, fairly complete 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 0%, so the description must compensate. It adds meaning for 'weeks' (current, historical, core state) and 'include_players' (large catalog refresh, caching). 'league_id' is not explained, but its purpose is easily inferred from the name. Overall, good compensation for schema lack.

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 'Synchronize broad Sleeper league state for setup and season-long operation,' using a specific verb and resource. It differentiates from sibling tools like sync_draft and sync_league_history by emphasizing broad league state and supporting historical/backfill via weeks parameter.

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 provides explicit guidance on parameter usage: omitting weeks captures current NFL week, explicit weeks for historical/backfill, empty list for core state, and include_players only for refreshing the player catalog. It does not explicitly mention alternatives or when-not-to-use, but the parameter behavior is well described.

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