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

Annotations already declare readOnly/idempotent/non-destructive. The description adds real interpretive value: it explains that questionable players' proj/ceiling/minutes are play_p times the if-plays line, and names the if_plays_* columns - behavior an agent couldn't infer from annotations alone.

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?

Front-loaded with what the tool returns, then roster format, then the projection caveat. Dense but every sentence carries information relevant to interpreting the result.

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 does explain the key return columns (play_p scaling and if_plays_* fields), which is valuable. But it omits the meaning of both input parameters and any pagination/scope behavior for slate selection, leaving meaningful gaps.

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% and the description never mentions the two parameters (slate_id, min_projection) or their format/effect. It describes output columns instead of input semantics, so it fails to compensate for the undocumented schema.

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 specifically that it returns the full NBA DraftKings classic pool for one slate in compact form, with DK ids, and describes the roster format. Clear verb+resource, though it doesn't explicitly differentiate from siblings like invoke_nba_player_index or invoke_nba_projections.

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?

Implies usage for lineup building via the roster format and $50,000 cap context, but never explicitly says when to use this vs invoke_nba_projections, invoke_nba_player_index, or invoke_nba_optimizer. No exclusions or prerequisites stated.

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