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 two useful behavioral facts: the set of returned metrics and the pre-season no-slate response. It does not describe pagination, rate limits, or how the plan limit interacts with results.

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 compact sentences, front-loaded with the core purpose and returning-metrics list. The second sentence, the pre-season behavior, earns its place as an edge-case warning, though it is slightly tangential.

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 names the returned metrics. But for a six-parameter tool with 17% schema coverage, it leaves most filter semantics undocumented, so an agent still lacks enough information to filter by team, player, position, or slate.

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 17% (only 'limit' is documented), leaving team, player, position, slate_id, and sort_by without explanation. The description lists output fields rather than clarifying input filters, and only implicitly hints at slate_id via 'main DraftKings classic slate'. It does not compensate for the coverage gap.

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 and resource ('NBA DFS projections') and enumerates the returned metrics (minutes, DK points, floor, ceiling, value, ownership, salary, injury status), which is informative. It also scopes the source to the main DraftKings classic slate. It does not, however, explicitly separate itself from nearby siblings like invoke_nba_player_pool or invoke_nba_props.

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 explicit when-to-use guidance and no alternatives named among the many projection/pool/optimizer siblings. The only usage-adjacent statement is the pre-season edge case ('Before the season it says no slate is built yet'), which is helpful but not routing guidance.

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