Find similar photos

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

With no annotations, the description carries the full burden and does so admirably. It discloses output formatting (Markdown links, inline thumbnails), behavior in certain clients (thumbnails in expandable panel), and explicitly warns against blaming ad-blockers. This is rich behavioral context that annotations alone would not provide.

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?

Although lengthy, every sentence delivers necessary guidance. The description is well-structured with clear sections (PRESENTING RESULTS, RANKS & SIMILAR) that are front-loaded with the most critical usage trigger. No filler or repetition.

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 tool is complex (UX-heavy, pagination, output formatting) and the description covers all key aspects: when to use, parameter sourcing, rank mapping, result presentation, user interaction, and pagination. With an output schema present, return-value details are already covered, so the description is complete.

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 schema already has clear descriptions for both params, but the description adds significant context: it explains that photo_id comes from a previous search and shows how to derive it from rank, and cursor comes from pagination.next_cursor. This goes beyond the schema's own wording.

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 is extremely clear: it states the tool finds similar photos and explicitly lists trigger phrases ('find something similar', 'show me more like this'). It distinguishes from sibling tools by requiring a photo_id from a previous search, not an initial search.

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?

Provides explicit when-to-use instructions and even says when not to use (don't ask for id, map rank yourself). It also gives step-by-step guidance for handling user rank requests and never asking for photo_id, which goes beyond simple usage to a complete protocol.

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