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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds substantial context beyond them: the 20-clips-per-page pagination contract, the meaning of `in_rss_playlist`, the explicit statement that audio is not fetched or returned, and the warning that the archive may be inactive. This is exactly the extra behavioral detail the annotations cannot convey.

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?

Front-loads the resource and returned fields, then layers pagination, field semantics, and the freshness caveat in a compact block with zero filler. Dense but every sentence earns its place; slightly less scannable than a bulleted structure.

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?

An output schema exists so return values need not be explained, and the description still covers the operational essentials an agent needs: page size, cursor continuation, the non-obvious `in_rss_playlist` field, the absence of audio, and a staleness warning. Nothing material is missing for correct invocation.

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 100% and the single `cursor` param is documented there, so the baseline is 3. The description adds value by clarifying that the cursor value is the response's `next_cursor` and must be passed 'unchanged', linking the input parameter to the response field rather than just 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?

States a specific verb (List) and resource (public Quick Picks Daily clip metadata from the FanDuel Research archive) and enumerates the returned fields. It is clear and unambiguous, but it does not explicitly differentiate itself from the sibling `fanduel_research` tool, leaving the relationship between the two to inference.

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?

Provides concrete operational context: 'pass next_cursor unchanged to continue' and 'check published_at for freshness because this archive may be inactive' help the agent decide whether/how to use it. It stops short of naming alternatives or explicit when-not conditions, so it does not reach the top tier.

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