sleeper: Get league rosters

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered by structured data. The description adds useful context by listing the data shape returned (owners, player_ids, wins/losses, points), but discloses nothing about auth, rate limits, or how partial/empty leagues behave.

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?

A single tight sentence that front-loads the operation and immediately qualifies the returned fields. Nothing is wasted and there is no filler.

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 simple single-required-param read tool with annotations covering safety and no output schema, the description is nearly complete; it compensates for the missing output schema by naming the return fields. It falls short only on usage routing relative to siblings.

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 both parameters (league_id, fields) are already documented in the schema. The description adds no syntax or format detail for league_id or the fields projection, leaving the schema to do the heavy lifting - the correct baseline of 3.

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?

States a specific verb (get) and resource (league rosters), and enumerates the returned content (owners, player_ids, wins/losses, points), so the agent knows exactly what it fetches. It does not, however, explicitly distinguish itself from near siblings like sleeper_get_league_users or sleeper_get_league_matchups.

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?

Usage is only implied by the name and the description's mention of 'in a league'; there is no explicit when-to-use statement, no exclusions, and no routing to alternatives such as get_league_users or get_league_matchups.

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