get_draft_context

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

With no annotations, the description must carry the burden of behavioral disclosure. It lists the data categories bundled, implying a read-only aggregation operation, but it never explicitly states that it is non-destructive or that it does not modify any state. It also does not mention performance or rate-limit implications despite aggregating many data points.

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 two concise sentences, front-loaded with the key phrase 'One-call snapshot'. It lists the bundled components in a clear, scannable list and wastes no words. Every sentence earns 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?

While the description covers the main content categories, it omits the parameter explanation and provides no hint about the output structure. Since there is no output schema, the agent is left without information on how the response is formatted or how to interpret the bundled data.

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 schema has 0% description coverage and the tool description does not mention the 'top_per_position' parameter at all. The agent has no guidance on how to set this value beyond its name and default, making correct invocation a guess.

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 it is a 'One-call snapshot' that bundles draft state, roster needs, best available players, ADP fallers, etc. This makes the purpose unambiguous and distinguishes it from sibling tools that focus on individual data sources like get_draft_state or get_available_players.

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?

It explicitly says 'when you are on the clock' and 'everything needed to make a pick inside a 60-90 second clock', conveying the ideal usage scenario. However, it does not explicitly mention when not to use it or direct to alternatives for more granular data, leaving some ambiguity about edge cases.

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