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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false; the description's 'opens nothing by itself' is consistent but largely redundant. The one genuinely additive disclosure is that the payload is a step-by-step procedure rather than photo data — useful, yet it conflicts with the tool's own name. Nothing is said about the shape or length of the returned steps.

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 final sentence — Unsplash REST API v1, mcp.unsplash.com, Claude directory listing, 'checked 6 Nov 2026' — is background trivia that does nothing for tool selection or invocation. The core behavioral fact (returns instructions, not data) is buried in the middle clause rather than front-loaded.

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 tool the description carries the entire burden, and it leaves the central question unanswered: since there are no arguments, how does the agent convey which photo it wants details for? The definition is long but spends its length on API trivia and name/behavior mismatch instead of resolving that 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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no inputs are needed, and there is nothing the schema could have covered that is missing. There is, however, no indication of how the caller specifies which photo is being looked up — presumably via the browser session, which is left unexplained.

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 title promise 'Get photo details,' but the body says the tool 'Returns how to do it in Unsplash step by step (screens, buttons, fields) and opens nothing by itself' — an instruction/guide tool, not a data-fetch tool. An agent reading only the first clause would expect photo metadata back; the actual behavior only surfaces mid-sentence. No distinction is drawn from cotlet_app_guide or unsplash_search_photos.

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 route the caller onward ('then do it with the cotlet_browser_* tools in the user's Unsplash Cloud Browser'), which is real sequencing guidance. But it never says when to prefer this over calling Unsplash's API directly, nor when to use it instead of the sibling search tools it mentions nothing about. Usage is implied rather than stated.

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