Get Draft Picks

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

With no annotations present, the description carries the full burden and does add context: it discloses that the response includes player metadata (name, position, team), and 'Get' implies a read-only operation. However, it says nothing about pick ordering, behavior for an invalid or nonexistent draft_id, or auth/rate-limit expectations, so the behavioral picture is only partial.

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?

Two short sentences with no filler; the core action is front-loaded and the second sentence earns its place by revealing that player resolution is bundled into the response. Nothing is redundant or wasteful.

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 is simple (one required string parameter) and the description covers the core behavior, but with no output schema or annotations, an agent gets no hints about pick ordering, the shape of each pick object, or how this relates to get_traded_picks. Adequate for basic invocation, with clear gaps around return format and edge cases.

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% — the only parameter, draft_id, is already documented as 'The Sleeper draft ID.' The description's phrase 'in a draft' merely echoes this meaning and adds no format, validation, or source detail, so the schema-heavy baseline of 3 applies.

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?

States the verb 'Get' with a specific resource: 'all picks in a draft,' and clarifies the response includes player metadata. The phrase 'all picks' implicitly sets it apart from the sibling get_traded_picks, but no sibling is named and the differentiation is left to inference.

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 is purely declarative and gives no guidance on when to call this versus siblings such as get_traded_picks or get_drafts. No context is provided on the typical flow (e.g., fetch a draft via get_drafts first) or when the bundled player metadata would make a separate resolve_players call unnecessary.

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