Get league overview

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

Annotations already declare 'readOnlyHint: true', so the description adds value by specifying the returned data (teams, settings, standings). It also reveals the default behavior when the parameter is omitted. No destructive actions or additional safety concerns are indicated.

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 a single sentence, highly concise, and places the core action first. Every word contributes meaning without 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?

Given the tool's simplicity (one optional parameter, no output schema, read-only annotations), the description covers the essential aspects: what it returns and the default behavior. It could mention that the standings are current or that this is the primary overview endpoint, but it is adequate.

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 schema provides 100% coverage for the single parameter, but the description adds important semantics: the parameter is optional and defaults to the configured league. This clarifies usage beyond the schema's brief example.

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 retrieves a league's teams, settings, and current standings. It uses a specific verb ('Get') and resource ('league overview'), effectively distinguishing it from siblings like 'get_teams' or 'get_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?

The description mentions defaulting to the configured league when 'leagueKey' is omitted, providing some usage context. However, it does not explicitly guide when to use this tool versus alternatives such as 'get_teams' for detailed team info or 'get_matchups' for matchups.

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