List collections

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine context beyond that: the scope is the archive's curated/themed set (not arbitrary user buckets) and each entry carries a slug and shot count, which tells an agent what it gets back. It does not state whether this is the complete list or how large the result can be.

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?

A single sentence with zero waste, front-loading the verb and resource while packing the payload description and examples into the same clause.

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 no-parameter, no-output-schema read tool, the description supplies what the agent most needs: what a 'collection' is here and what fields come back. The only gap is whether the list is exhaustive or bounded, and no sorting/order guarantee is given.

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?

Zero parameters, so the baseline is 4 and the schema carries nothing to explain. The description's mentions of slugs and shot counts describe the response rather than inputs, which adds mild value but is not required parameter guidance.

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 (the archive's curated, themed collections of shots) and even names the payload (slugs and shot counts). The enumeration framing, plus concrete examples (Cats, Film Countdowns, Space Flight), makes it unmistakably the browse-all endpoint rather than get_collection or search_clips.

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?

Usage is only implied: it takes no parameters, so an agent can infer it is a safe discovery/browse call made before drilling into get_collection or search_clips. The description never says when to use this versus those siblings, nor that it is the prerequisite step for obtaining a collection slug.

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