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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description stays consistent with them by saying it 'opens nothing by itself'. Beyond that, it adds genuinely non-obvious behavior: the return value is procedural text listing screens, buttons and fields rather than photo records. That disclosure is what an agent most needs to avoid misusing the result.

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 first two sentences are front-loaded and earn their place. The third sentence, a mini-FAQ about Unsplash's public REST API v1 and the hosted MCP server at mcp.unsplash.com, is unrelated to invoking this tool and dilutes the definition.

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 no input schema and no output schema, the description must carry everything, and it partly does by explaining the guide-then-browser workflow. It never resolves the central ambiguity of a zero-parameter tool called 'list collection photos': which collection, and how the agent should proceed when the user has multiple collections.

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?

There are zero parameters, so the baseline is 4 and there is nothing schema-side to compensate for. The description adds no parameter meaning, but none is needed; its only weakness is never explaining how the target collection is identified when no argument exists.

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 name and opening phrase say 'list collection photos', but the description then reveals the tool actually returns step-by-step instructions rather than the photos themselves ('Returns how to do it in Unsplash step by step'). That reframing is valuable, yet the verb/resource mismatch leaves the agent unsure whether calling it yields data or a guide. It also never distinguishes itself from siblings like unsplash_search_collections or unsplash_get_photo_details.

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 does state the follow-up path: use the cotlet_browser_* tools in the user's Unsplash Cloud Browser after reading the guidance. However, it gives no criteria for choosing this tool over unsplash_search_collections or the mentioned official Unsplash API/MCP server, and no prerequisites or exclusions are stated.

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