search_unsplash_photos

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It reveals that results are royalty-free and lists the return fields (resolutions, dimensions, etc.), which is helpful. However, it does not mention behavioral aspects such as pagination behavior, rate limits, or whether the operation is read-only.

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 description is a single, well-structured sentence that front-loads the primary purpose and then concisely lists key return attributes. Every word contributes meaningful information, with no redundancy or 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?

The description is sufficient for selecting the tool correctly, covering the main purpose and key return data. With a comprehensive input schema and an output schema present, the description does not need to detail all parameters or return schema. It lacks explicit usage guidance but that is handled separately in the usage dimension.

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 input schema has descriptive text for all 8 parameters, achieving 100% coverage. The tool description adds no additional parameter-level meaning beyond what the schema already provides, so it meets the baseline of 3 for high schema coverage without exceeding it.

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 clearly states the tool's purpose with a specific verb ('Search') and resource ('photos on Unsplash'), and distinguishes it from sibling tools by focusing on photo search rather than downloads or collection search. It also lists valuable return data attributes.

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 description implies this tool is for finding photos, but it does not explicitly state when to use it versus sibling tools like search_unsplash_collections or download_unsplash_media. No exclusions or alternative recommendations are provided, leaving usage guidance implicit rather than explicit.

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