get_league_info

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

With no annotations, the description carries the full burden. It usefully discloses that the league is resolved from SLEEPER_LEAGUE_ID (default value given), which is real behavioral context, but it does not state the read-only nature, failure behavior when the env var is unset, or whether results are cached.

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 and the bulleted field list is scannable, but the closing 'Returns: Dict containing all league configuration and settings' restates the opening clause and the field bullets, which is mild redundancy.

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 the description need not explain the return shape, and there are no parameters to document. The enumerated fields plus the env-var note make it sufficiently complete for a zero-argument read tool, though a read-only cue would round it out.

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 tool takes zero parameters, so per the rubric the baseline is 4. Nothing about argument semantics can be missing here, and the env-var note is the only input-side detail worth mentioning.

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+resource ('Get comprehensive information about the Token Bowl fantasy football league') and enumerates the exact settings returned, which cleanly separates it from siblings like get_league_rosters or get_league_matchups. It is clear but never explicitly contrasts itself with those siblings.

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?

There is no when-to-use guidance, no conditions, and no mention of alternatives despite a large family of get_league_* siblings. The agent must infer that this is the settings/config call rather than, say, rosters or matchups.

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