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 fully covered and the description is not obligated to restate it. It adds the scope constraint of a single game and the captain-mode format, but says nothing about defaults, pagination behavior, or what happens when neither selector is supplied. No contradiction with annotations.

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 sentences: the first front-loads the payload contents, the second gives invocation footwork. Nothing is repeated or wasted, and the highest-value information (what data comes back) leads.

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 the returned metrics (flex/captain salary, projection, ceiling, ownership, optimal captain rate, leverage). The remaining gap is that zero parameters are marked required, so the description only loosely signals that slate_id or game must be provided, and it omits default/pagination behavior.

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 coverage is 67% and the slate_id property has no schema description at all; the description compensates by stating that slate_id and game are alternate selectors, which is semantics the schema does not convey (and neither is listed as required). It adds the example format for game, matching the schema, but gives no guidance on the limit parameter.

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 product and format ("DraftKings NFL Showdown (captain mode) pool for one game") and enumerates the returned fields, so an agent can tell it apart from generic siblings like invoke_nfl_player_pool or invoke_nfl_ownership_by_contest. It does not explicitly name the closest alternatives, so it falls short of a 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?

The only routing guidance is "Pass slate_id or a game like ATL@GB," which is parameter advice rather than a when-to-use statement. No condition, prerequisite, or named alternative (e.g., invoke_nfl_optimizer, invoke_nfl_list_slates) is given for choosing this tool.

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