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

The key behavioral disclosure ('opens nothing by itself', returns screens/buttons/fields) is valuable and consistent with readOnlyHint=true and openWorldHint=false. However, with zero parameters the description never explains how the target photo and collection are identified — presumably the returned guidance is generic — which is the main thing an agent needs to know before calling.

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 useful, stating the resource, the non-action behavior and the follow-up tools. The final sentence about Unsplash's public REST API and hosted MCP server is off-topic for invocation and adds noise.

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 is the only source of return-value information, and it only loosely characterizes the output as step-by-step screens, buttons and fields. It is adequate to avoid misuse as a mutation tool but leaves ambiguity about how photo/collection context is supplied.

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 takes no parameters, so the schema carries no semantic burden; baseline applies. The description makes clear the call is parameterless by describing a fixed, generic set of return steps.

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 verb and resource (add a photo to a collection) and then corrects the naive reading by saying it returns step-by-step instructions rather than performing the action. That distinguishes it from siblings like unsplash_list_collection_photos or unsplash_create_collection, though the naming still implies an action tool.

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 tells the agent the follow-up path: get the steps here, then execute them with cotlet_browser_* tools. It does not explicitly say when not to use it, or how this compares with the Unsplash REST API / mcp.unsplash.com it mentions, so the agent must infer the routing decision.

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