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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, and the description adds real behavioral context beyond them: page size of 24, that GIFs stream from KLIPY and are never stored by LFG, and that a no-match search returns a note rather than an error.

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?

Front-loads the core action and the empty-query behavior in the first clause. The remaining sentences are dense but each carries information; "the address and id a GIF wallpaper takes" is slightly awkward phrasing but not padding.

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?

With no output schema, the description usefully covers the return shape (address and id per result) and the empty-result case. It does not mention pagination bounds (max page 20) or result ordering, minor gaps for a two-parameter search tool.

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 both parameters (page of 24, query with empty=trending) are already documented in the schema. The description's "24 to a page" and empty-query behavior restate the schema rather than adding syntax or format detail, so baseline 3 applies.

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?

States a specific verb+resource ("Searches KLIPY's GIFs for a wallpaper") plus the alternate trending mode, and carves out scope by noting LFG's own sounds and looks are a separate search. It never names the sibling tool that handles that other search, so differentiation is implied rather than explicit.

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?

Clearly explains the two modes: search for a wallpaper when a query is given, trending when the query is empty. It also signals that this tool is not for LFG's own sounds/looks, but stops short of naming the alternative or stating explicit exclusions.

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