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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context on top: 'Data refreshes every 30 minutes' discloses freshness/latency, 'Defaults to the main slate' discloses default scope, and 'DraftKings scoring' pins the scoring model. It does not mention plan limits or pagination, but the added context is substantive.

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?

Purpose is front-loaded in the first clause, followed by the field inventory and two short operational notes. The long field enumeration is dense but does real work since no output schema exists. No filler or repetition.

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 carry the return-shape burden by listing the projected fields, which is valuable. However it leaves gaps around pagination behavior and plan limits that the params imply, and gives no sense of row volume or sorting defaults for a nine-parameter query tool.

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 description coverage is 89%, so the schema already documents nearly all nine parameters, including the contest_type multipliers and offset paging. The description confirms the slate default (relevant to slate_id) and the scoring model, but adds little parameter-level meaning beyond what structured fields carry. Baseline 3 applies.

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 names the resource and scope — 'NHL DraftKings projections for one classic slate' — and enumerates the exact fields returned (salary, DK points, floor, ceiling, TOI, etc.). An agent can tell this is a player-level projections feed rather than a pool, optimizer, or odds feed. It stops short of naming a sibling like invoke_nhl_player_pool to sharpen the boundary, so a 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance relative to the many sibling tools (invoke_nhl_optimizer, invoke_nhl_player_pool, invoke_nhl_lines). 'Defaults to the main slate' describes a default, not a selection rule. The agent must infer usage from the field list alone.

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