Get Draft Details

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, fully covering safety. The description adds behavioral context by listing returned fields (type, status, rounds, etc.), which goes beyond what annotations offer.

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 and well-structured: one sentence for purpose, then an Args section, Returns section, and examples. Every part adds value, and it is front-loaded with the main action.

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 tool's simplicity (one required parameter), rich annotations, and no output schema, the description fully covers what the tool does and returns. The listed return fields provide sufficient context for an agent.

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% with a description for draft_id. The description repeats the schema information ('draft_id (string): The Sleeper draft ID') but adds no new semantics beyond examples. With full schema coverage, 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 'Get detailed information about a specific Sleeper fantasy draft,' which uses a specific verb and resource. It distinguishes from sibling tools like sleeper_get_draft_picks and sleeper_get_league_drafts by focusing on a single draft's details.

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 illustrating when to use the tool (e.g., 'Show details for draft 987654321'). While it doesn't explicitly state when not to use or list alternatives, the context from sibling tool names and the single required parameter make usage clear.

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