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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that results are single-game captain-mode rows with DK ids and injury status, but says nothing about pagination interplay with limit or what include_out changes. Adds some value beyond annotations, but not rich behavioral context.

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 the resource and returned fields, then the invocation hint. The field enumeration is dense but scannable; nothing is padding.

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, the description usefully lists returned fields, and it explains the game/slate_id entry points. However, for a 4-parameter tool with 25% schema coverage, one parameter (include_out) is undocumented in both places and limit semantics are only in the schema, leaving an agent to guess.

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 only 25% (only 'limit' is documented), so the description must compensate. It clarifies the 'game' parameter format (MIN@NYL) and the slate_id alternative, but leaves include_out entirely unexplained and does not state whether slate_id and game are mutually exclusive. Partial compensation at best.

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: the DraftKings WNBA Showdown pool in captain mode, scoped to a single game, and enumerates the fields it returns. The 'for one game' + 'captain mode' framing implicitly distinguishes it from the full-slate invoke_wnba_player_pool, though it never names a sibling explicitly.

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 only guidance is invocation-level: 'Pass slate_id or a game like MIN@NYL.' There is no statement of when to choose this over invoke_wnba_player_pool, invoke_wnba_projections, or invoke_wnba_optimizer, and no exclusions. Usage is implied rather than specified.

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