Get League Drafts

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds that it returns 'type, status, rounds, and timing' but does not disclose additional behavioral traits (e.g., pagination, data recency). With annotations covering safety, a 3 is appropriate.

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 concise with clear sections (Args, Returns, Examples) and no fluff. Every sentence provides value.

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 simple single-parameter retrieval task, rich annotations, and no output schema, the description adequately covers what the tool returns (type, status, rounds, timing) and examples. It is complete for agent decision-making.

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 coverage is 100% for league_id. The description repeats 'The Sleeper league ID' with no added meaning (e.g., format, source). Baseline 3 is justified as schema does the heavy lifting.

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 'Get all drafts that have taken place in a Sleeper fantasy league,' using a specific verb and resource. It distinguishes from siblings like sleeper_get_draft (single draft) and sleeper_get_draft_picks (picks of a draft). Examples reinforce the purpose.

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 provides examples but does not explicitly guide when to use this tool versus alternatives (e.g., sleeper_get_draft for a specific draft, sleeper_get_user_drafts for user-level drafts). The context is implied but not differentiated.

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