get_draft_data

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'Read a draft' language is consistent and there is no annotation contradiction. The description adds one behavioral nuance—membership verification as a prerequisite—but says nothing about error behavior, rate limits, or what happens if the draft is not in the league.

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 front-loaded sentence: 'Read a draft' comes first, and the membership verification clause adds meaningful context without fluff. It is concise and every word earns its place, though it is slightly under-specified, so it misses a 5.

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 has three required parameters and no output schema, so the description should provide enough context for a correct call, including how the parameters relate and what the available resource values provide. It only states the draft's membership precondition, leaving resource semantics and return expectations unexplained.

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?

The input schema has 0% description coverage, so the description must compensate, but it only clarifies the league-id/draft-id relationship via 'membership in the selected league.' It does not explain draft_id, league_id, or what each resource enum value returns, leaving most parameter meaning to the raw property names and the enum.

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 uses a specific verb ('Read') and names a target resource ('a draft'), making the tool's core purpose clear and distinct from many siblings such as get_league_data or get_nfl_state. It stops short of 5 because it does not specify what kinds of draft data (details, picks, traded picks) are returned, leaving the schema enum to carry that load.

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 'after its membership in the selected league is verified' provides an implied precondition: call this only once you have confirmed the draft belongs to the selected league. There is no explicit guidance on when not to use it or how it compares to sibling read tools like get_league_data, so it does not fully earn a 4.

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