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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is credited for what it adds beyond them: a 30-minute refresh cadence, the default main-slate behavior when slate_id is omitted, DraftKings scoring, and the classic vs showdown roster structures. Useful operational context an agent could not get from the schema.

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 long field enumeration is dense and reads as one run-on sentence, but it is front-loaded with the resource definition and every clause carries information (fields, defaults, roster formats, refresh rate). Minimal waste, slightly list-heavy rather than prose.

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 must carry the return-shape burden, and it does by naming the returned fields. Pagination and limit semantics are documented in the schema rather than the description, which is acceptable. Complete enough for a 0-required-param read tool.

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?

With 100% schema description coverage the baseline is 3, but the description goes further by fixing the domain meaning of the position enum values, the CPT salary 1.5x multiplier, and the slate_id default. It adds real semantics rather than restating the schema.

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?

The description states a concrete resource with its scope: 'The DraftKings League of Legends pool for one slate', and enumerates the exact fields returned (salary, CPT salary, projections, DK ids), which separates it from a generic projections tool. It never names a sibling to route against, so the agent must infer the difference from invoke_lol_projections rather than being told.

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?

'Without slate_id it returns the main slate and lists the other slates' gives real default behavior context, and the classic/showdown roster strings suggest when each format applies. However there is no explicit when-to-use-this-vs-an-alternative guidance, no note on chaining with invoke_lol_optimizer, and no exclusions.

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