get_draft_state

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

The description discloses two behavioral aspects: the tool is never cached, and it is safe for frequent polling. These facts imply a read-only, low-risk operation, giving the agent confidence about side effects and performance.

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 extremely concise, consisting of two short sentences. Every word adds value, covering the tool's output and usage guidance without any fluff.

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 description provides sufficient context about what the tool returns and how frequently it can be called. It omits details about the output format or potential error conditions, but for a simple state retrieval tool, the information is adequate.

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 tool takes no parameters, so there is nothing to describe. The schema already reflects this, and the description adds no unnecessary parameter details. Perfect score 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 the tool returns live draft state including picks made, who is on the clock, and the user's next picks. Though it uses a noun phrase instead of an explicit verb, the intention is unambiguous and distinct from sibling tools like get_draft_context.

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 explicitly notes the tool is never cached and is safe to poll every few seconds during a live draft. This provides clear guidance on when to use it, though it does not contrast with alternatives or state when not to use it.

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