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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered; the description adds real behavioral context beyond that — ruled-out players are omitted, the refresh cadence is 30 minutes, the default slate is the main one, and the exact field set returned.

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 payload contents are front-loaded in the first sentence and the remaining sentences (exclusions, default slate, refresh, scoring) each add distinct facts. The long inline field list is dense but not redundant.

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 correctly carries the burden of describing return values by enumerating the player fields and the stack objects, and it also states the scoring system and exclusion rule. Only usage-vs-sibling routing is left thin.

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 100%, so team, offset, position, slate_id, contest_type and min_projection are already documented in the schema. The description only adds that the pool is 'compact' and that team returns the whole pool, which is marginal value over the structured fields.

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 verb+resource (retrieves the full NHL DraftKings classic player pool for one slate) and enumerates what is returned, so an agent can distinguish it from invoke_nhl_projections, invoke_nhl_lines and invoke_nhl_optimizer without opening any schema.

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?

Gives useful operating context (defaults to the main slate, ruled-out players are excluded, data refreshes every 30 minutes, Fan returns the whole pool) but never says explicitly when to choose this over sibling pool/projection tools or what the free-plan limitation means for results.

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