Get League Rosters

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

Annotations already declare readOnlyHint=true, destrcutiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it returns owner IDs, player lists, and win/loss records, but does not disclose additional behavioral traits beyond what the annotations imply.

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 concise, with a clear opening sentence, structured Args/Returns/Examples sections. It is front-loaded and contains no unnecessary text, though examples could be slightly more informative.

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, read-only) and the annotations covering safety, the description adequately explains what is returned and provides examples. Lacks mention of pagination or rate limits, but these are not critical for this 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 coverage is 100% for the single parameter league_id, which already has a description 'Sleeper league ID'. The description merely repeats this without adding new semantic meaning, so baseline score of 3 is appropriate.

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 gets all rosters in a Sleeper fantasy league, including players, starters, and standings. It uses a specific verb and resource, and its purpose is distinct from sibling tools like sleeper_get_league or sleeper_get_league_users.

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 examples showing when to use the tool ('Show me all rosters'), but does not explicitly mention when not to use it or contrast with alternatives. No guidance on using sibling tools.

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