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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the fallback behavior (most recent clips) and the scope switch on episodeSeq, but says nothing about ordering guarantees, result limits, or total-count behavior beyond the schema's pagination fields.

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, no filler, with the primary purpose front-loaded and the branching behavior placed second. Every clause carries information.

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?

For a read-only list tool with complete schema coverage and annotations carrying the safety profile, the description supplies what the structured fields do not: the default result set when episodeSeq is omitted. Return-value shape is not covered and no output schema exists, but for a standard list this is a minor gap.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by framing episodeSeq as a mode switch between episode-scoped listing and a default most-recent listing, which clarifies the otherwise undocumented default result set.

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') plus resource ('the user's clips') and even defines the domain term in parentheses ('saved key moments with AI takeaways'), which lets an agent distinguish this from get_clip, create_clip, and delete_clip without opening a schema.

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?

Gives an explicit conditional: pass episodeSeq to scope to one episode, otherwise it returns the user's most recent clips. This is clear usage context, though it never names alternative siblings or states exclusions for when this list should not be used.

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