sleeper_find_leaguesLists the NFL leagues a Sleeper username belongs to, so a league id can be picked for the other league tools. Muffed stores nothing about who called it.
| Name | Required | Description | Default |
|---|---|---|---|
| season | No | ||
| username | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds a privacy note ('Muffed stores nothing about who called it') which is useful context, but it does not describe return format or error behavior. With annotations covering the safety profile, this is consistent with a score of 3.
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 two sentences: the first front-loads the main purpose and the second adds a meaningful privacy statement. No redundant or extraneous content is present.
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 tool has a required (username) and optional (season) parameter, no output schema, and useful annotations. However, the description does not explain the optional season parameter, the return format, or potential error cases, leaving significant gaps for an agent to use the tool correctly.
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 description does not explain any parameters. It indirectly references 'username' but completely omits the 'season' parameter, leaving the optional parameter undocumented. This fails to compensate for the lack of schema descriptions.
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's purpose with a specific verb ('Lists') and resource ('NFL leagues a Sleeper username belongs to'). It also distinguishes itself from sibling league tools by indicating its role in picking a league id for other tools.
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 implies when to use the tool ('so a league id can be picked for the other league tools') and suggests a workflow order. However, it does not explicitly state when not to use it or mention any alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: entity metrics, metric definitions, leaderboards, comparisons, backfield info, editorial insights, claim verification, and five separate Sleeper league tools each with a clear purpose. No two tools could be easily confused.
All tool names use snake_case and follow a predictable verb-noun pattern (get_, list_, query_, compare_, verify_) with the sleeper_* prefix consistently applied to fantasy-league tools. The naming convention is uniform throughout.
13 tools is within the ideal 3-15 range and matches the server's dual purpose of verified NFL stats and fantasy context. Every tool serves a clear function without redundancy or bloat.
The tool surface comprehensively covers the stated domain: metric retrieval, definitions, listings, leaders, comparisons, backfield context, insights, claim verification, and fantasy league operations. No obvious dead ends or missing core operations.