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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: a cap of 80 results, the exact metadata fields returned, and the fact that images themselves are not returned. The trailing 'Trvlrr Plus' hints at a plan/premium gate but is too cryptic to count as clear auth disclosure.

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?

Two tight sentences, front-loaded with the verb and examples, followed by the return contract. No 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?

An output schema exists, yet the description still summarizes return fields and the 80-item cap, leaving little ambiguity for a one-parameter search. The only unclarified element is the ambiguous 'Trvlrr Plus' tag.

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 covers the single 'query' parameter at 100%, and the description goes further by showing the natural-language style expected ('describe them' plus sample phrases), which helps the agent construct good queries beyond the bare 'What's in the photo.'

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?

Specific verb+resource ('Find photos') with concrete query examples and an explicit statement of what is returned. Nothing among the siblings (trips, items, stats, file) overlaps, so the agent can route to it unambiguously.

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 example queries ('lighthouse', 'ramen', a person's name) give clear context for when this tool applies, and the metadata-only return is spelled out. There is no explicit when-not or alternative tool named, but no sibling competes for this job.

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