get_league_drafts

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

No annotations are present, so the description carries the full behavioral burden. It clearly conveys a read/retrieval operation and enumerates return contents, but relies on the conventional meaning of "Get" to signal read-only and does not state edge cases (e.g., empty list when no drafts) or auth requirements.

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 bullet list is scannable, but the bullet list of draft fields is then restated by a redundant "Returns: List of draft dictionaries for all league drafts" line that adds no new information. Moderate waste.

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 return values need not be spelled out, yet the description still enumerates them helpfully. For a zero-parameter read tool this is essentially complete, missing only minor edge-case/auth detail.

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, which establishes a baseline of 4. The only parameter-like reference (draft_id) belongs to the related get_draft_picks() tool, so there is nothing to clarify here.

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 uses a specific verb + resource ("Get all draft information for the Token Bowl league") and scopes it to league drafts, which distinguishes it from generic siblings like get_league_info. It names the related get_draft_picks() tool, clarifying the boundary of what this tool covers. It does not, however, contrast against the other roster/matchup/transaction siblings explicitly.

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?

It provides one routing hint: use draft_id with get_draft_picks() for pick-level detail, implying this tool is the summary-level entry point. There is no explicit when-to-use/when-not guidance or comparison to the other league siblings. Usage is implied rather than stated.

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