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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds the default-slate behavior ("Defaults to the DK main slate"), which is useful beyond annotations, but says nothing about pagination, rate limits, or how limit interacts with the plan cap.

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 and the metric list is dense but informative, followed by a short default note. The long enumeration of projected fields is somewhat heavy, but every item maps to a real output field, so it earns its place.

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?

No output schema exists, so the description carries the burden of describing returns, and it does so thoroughly by naming all projected metrics. Combined with annotations covering the safety profile and the schema covering most parameters, the definition is largely complete, with only minor gaps around pagination and default limits.

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 57%, an intermediate level, giving a baseline of 3. The description reinforces the site parameter via the slate framing but does not clarify sort_by, limit, slate_id, team, position, or include_out beyond what the schema already conveys.

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 resource (NFL DFS projections) and enumerates exactly what is projected: median, floor, ceiling, ownership, boom/bust rates, value, Vegas total, spread, injury status. An agent can immediately distinguish this from siblings like invoke_nfl_sim_picks, invoke_nfl_player_pool, or invoke_nfl_optimizer.

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?

It specifies the applicable contexts (DraftKings classic slate, FanDuel main slate) and the default (DK main slate), which is real usage framing. However, it offers no explicit when-to-use/when-not-to-use guidance versus related NFL tools, so selection between siblings is left to inference.

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