unsplash_random_photo

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is largely covered. The description adds that results are random and optionally query-filtered, but does not mention access-key auth, rate limits, or Unsplash attribution expectations.

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?

It is a single, front-loaded sentence with no redundant or filler content. The core behavior and optional query are communicated efficiently.

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 simple read-only image retrieval tool with full schema coverage and clear annotations, the description covers the essential purpose. It leaves return-format details unstated, but there is no output schema and the schema already documents the parameters.

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?

Schema description coverage is 100%, so query, access_key, and orientation are already documented in the schema. The description only restates the optional query behavior and adds no further meaning for orientation or the required access key.

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: retrieving a random Unsplash photo, with optional query filtering. The word "random" meaningfully distinguishes it from unsplash_search_photos and unsplash_get_photo, though it does not explicitly name those siblings.

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?

The phrase "optionally matching a query" implies when the query parameter is useful, but the description does not explicitly say when to choose this over unsplash_search_photos or unsplash_get_photo. Usage is inferable from the name and description, but exclusions and alternatives are absent.

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