sleeper_league_rosters

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the description need not repeat those. It adds value by stating 'Auth: none needed' and including the exact return structure and a join hint, which are beyond what annotations provide. No contradictions with annotations.

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 compact and well-structured: a one-line summary, a return format, an example, and auth note. No superfluous words. Information is front-loaded, and the example is concrete.

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 the tool's simplicity (single parameter, no output schema), the description is complete: it outlines the return fields, provides an example call, and mentions authentication. It also gives a useful join hint for interpreting owner_id. No critical gaps remain.

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 only parameter, league_id, is fully described in the schema as 'League id. Required — part of the URL path.' The description adds an example value but does not significantly enhance the semantic meaning beyond the schema. With 100% schema coverage, baseline is 3, and the example is a minor bonus.

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 returns every roster in a league, including player IDs, starters, and season record. It distinguishes from sibling tools like sleeper_league (league info) and sleeper_league_users (user info) by specifying its focus on rosters. The verb 'get' is implied but the resource and scope are unmistakable.

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 usage by stating it returns rosters for a league, but it does not explicitly mention when to use this tool over siblings like sleeper_matchups or sleeper_league_users. No exclusionary or alternative guidance is provided, but the purpose is clear enough for an agent to infer appropriate invocation.

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