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

Annotations already establish read-only/idempotent/non-destructive, so the description's job is to add operational context. It does so by disclosing the exact returned field set, the DK classic roster slots, and the $50,000 cap / 2-game minimum, which meaningfully shape how the agent uses the result.

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?

Two sentences, front-loaded with what the pool contains, followed by the roster/cap constraints. Dense but no wasted phrasing; the field enumeration is informative rather than filler.

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?

With no output schema, listing the returned fields is valuable and largely covers the return contract. However, the zero-coverage parameters are left ambiguous, and there is no guidance on filtering or slate selection, so the definition is adequate but not complete.

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 0%, so the description carries the full burden for slate_id and min_projection. "Defaults to the main slate" gives some signal for slate_id, but min_projection is never explained (units, filtering direction, typical values), leaving half the parameters undocumented in both schema and description.

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?

States a specific resource (full WNBA DraftKings classic pool for one slate) and enumerates the returned fields, so an agent knows precisely what it gets. It does not explicitly differentiate itself from siblings like invoke_wnba_projections or invoke_wnba_list_slates, which leaves sibling selection to inference.

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?

"For one slate" and "Defaults to the main slate" imply the usage context (population of a slate for lineup building), but there is no explicit when-to-use versus alternatives such as invoke_wnba_optimizer or invoke_wnba_projections, nor any stated prerequisites.

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