Get Drafts

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

With no annotations provided, the description carries the full burden and does disclose one behavioral trait: results are sorted most recent to earliest. It does not explicitly confirm read-only behavior or mention limitations like pagination, though the verb 'get' and 'all drafts' imply a safe listing operation.

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 a single sentence of ten words with no filler. It front-loads the main action and scope, and the sort-order detail is the only addition, making every word earn 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?

This is a simple one-parameter read-style tool with no output schema, and the description covers the resource, scope, and sort order, which is largely sufficient. It does not explain the return shape or authorization needs, but the tool's simplicity and full schema parameter coverage keep the gap small.

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 100%, and the only parameter, league_id, is already described as 'The Sleeper league ID.' The description adds no new semantic detail about the parameter beyond tying it to the league context.

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 states a specific verb and resource—'Get all drafts for a league'—with the added precision of a sort order. It does not explicitly reference sibling tools, but 'drafts' clearly distinguishes this from get_draft_picks and other league-related tools.

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?

No guidance is given about when to use this tool versus alternatives like get_draft_picks. The description implies the usage scenario—retrieving drafts for a league—but provides no conditions, prerequisites, or exclusions.

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