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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and scope profile is settled. The description adds the shape of the result (per-collection image counts), but it doesn't say whether the list is exhaustive or paginated, how empty collections are treated, or anything about result size. Useful but not rich beyond what structured data already gives.

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, both load-bearing. The resource and its returned content are front-loaded, and the routing guidance follows immediately with no filler.

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 an output schema present and no parameters, the description carries only the routing burden, which it handles. The only residual gap is behavior at scale, which pagination or the output schema may already cover, but the description doesn't confirm that.

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?

The tool has zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. Schema coverage is 100% and the description correctly implies this is a no-argument call by saying nothing about inputs.

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 specific resource (collections in the store) with a concrete content payload (image count per collection), and it explicitly contrasts itself with search_images. An agent can distinguish this browsing tool from the sibling search tool without opening either 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?

It gives an explicit when: browsing with no particular search in mind. It also names the alternative, search_images, along with the condition that selects it (the person has described what they want). Both the positive and negative cases are covered.

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