get_draft_picks

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

With no annotations at all, the description carries the full burden. It does disclose the shape of the result (picks joined with player names and positions) and the read-only nature is inferable from "Fetch," but nothing is said about ordering, completeness across rounds, pagination, or authentication 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?

Two short sentences with the purpose front-loaded and the single parameter documented in a compact args block. The docstring-style formatting is slightly noisy but nothing is wasted and there is no filler.

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?

This is a simple single-parameter read tool with an output schema, so the description only needs to convey purpose and the parameter's format, both of which it does. The remaining gap — ordering/pagination of the returned picks — is minor given the output schema exists.

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 schema only gives the title "Draft Id," so the description meaningfully compensates by specifying it is the Sleeper draft ID and that it is a numeric string. It stops short of an example value or where to obtain the ID, which is why this is a 4 rather than a 5.

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 a specific verb and resource ("Fetch every pick in a draft") and adds that results are enriched with player names and positions, which distinguishes it from get_draft and get_draft_state by implication. It never names those siblings explicitly, so differentiation is clear but not spelled out.

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 phrase "every pick in a draft" implies the use case (full pick-by-pick retrieval rather than draft metadata or live state), but there is no explicit when-to-use guidance, no mention of get_draft/get_draft_state as alternatives, and no prerequisites or exclusions stated.

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