get_league_rosters

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

No annotations are provided, so the description carries the behavioral burden. It discloses the default include_details=false and exactly what each mode returns, including summary fields, player ID arrays, taxi/IR assignments, and keeper info, which is substantive for a read 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 purpose is front-loaded, but the description repeats return fields across the Args section, two 'When include_details' blocks, and a final Returns line. For a one-parameter read tool, this is unnecessarily long and redundant.

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?

The description covers the tool's scope, default behavior, and both output modes, which is enough to call it correctly. Since an output schema exists, the extensive return-value prose is redundant rather than necessary, and read-only intent is implied instead of stated.

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% and the single boolean parameter include_details has no schema-level description. The tool description fully compensates by defining the true vs. false behavior and enumerating the fields returned in each mode.

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 ('all team rosters in the Token Bowl league with player assignments'). The 'all team' scope implicitly differentiates it from the singular sibling get_roster, but no sibling is explicitly named, keeping it from a 5.

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?

No guidance is given on when to choose this tool over siblings like get_roster, get_league_info, or other league endpoints. It explains the include_details flag thoroughly, but that is parameter behavior, not tool-selection guidance.

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