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

Annotations already establish the safe read-only, idempotent profile, but the description adds genuinely non-obvious behavior: 'Premium returns the whole pool' (a tier gating detail) and 'Players ruled out are removed' (implicit filtering). These are real behavioral traits beyond the structured fields.

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?

Three tight sentences, front-loaded with what the tool returns and the fields it contains. The dense parenthetical field list is efficient, though it slightly crowds the opening sentence.

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 enumerates returned fields (name, position, team, opponent, salary, projection, ceiling, ownership, dk_player_id), so an agent knows the shape of the payload. The remaining gap is parameter-level detail for site and slate_id.

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 only 33% (only min_projection is documented), so the description should compensate. It implies a single-slate scope ('one slate') which maps loosely to slate_id, and 'under the salary cap' hints at salary/projection fields, but it says nothing about the site enum (dk/fd) or slate_id semantics.

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?

Names a specific resource (the full playable pool for one slate) and enumerates the returned fields, plus the concrete use case of building DK/FD lineups. It is clearly distinguishable from siblings like invoke_nfl_projections or invoke_nfl_optimizer, though it never explicitly contrasts itself with invoke_nfl_player_index.

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 phrase 'for building DraftKings or FanDuel lineups under the salary cap' implies the use case, but there is no explicit when-to-use-this-vs-alternatives guidance (e.g., versus invoke_nfl_projections for projections only, or invoke_nfl_optimizer). Usage is implied rather than stated.

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