get_draft

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds value by detailing the exact return contents (draft type, status, rounds, timer, slots, draft order, mapping, league ID, timing, metadata) and the intended workflow. No contradictions with annotations, and the description enriches behavioral understanding beyond the safety profile.

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?

Three sentences, zero filler. The purpose is front-loaded, followed by a concise list of returns, then usage guidance. Every sentence earns its place.

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?

For a single-parameter read-only tool with no output schema, the description covers purpose, parameter acquisition, return contents, and usage context. It is complete for an agent to call correctly: it knows what to expect and why.

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 covers 100% of the parameter, with its own description including provenance. The description repeats the sourcing guidance ('Obtain draft_id from get_league_drafts or get_user_drafts'), which is redundant with the schema. No additional semantics provided. Baseline 3 is appropriate.

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 it fetches settings and metadata for one Sleeper draft, distinguishing it from siblings like get_draft_picks (which fetch picks) and get_league_drafts (which list drafts). It also specifies the resource (draft) and the action (fetch), leaving no ambiguity.

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 clear guidance on when to use: 'Use before analyzing the board so pick positions can be assigned to users and rosters.' It also tells how to obtain the required draft_id from get_league_drafts or get_user_drafts. However, it does not explicitly state when not to use or name alternatives like get_draft_picks, though the context implies it. Minor gap.

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