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

The annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds real value on top by describing the result payload (ids, titles, page links, image links), the cap at `limit`, and the degenerate no-query behavior. It does not mention result ordering/relevance or what an empty match set looks like, which are the remaining behavioral gaps.

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?

Four short sentences, front-loaded with what is searched and immediately followed by when to use it, the return shape, and the follow-up tool. Nothing is repeated from the schema and no sentence is 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?

For a three-parameter, output-schema-less search tool the description covers scope, matching fields, return fields, and the empty-query case, which is nearly everything an agent needs. Minor omissions are relevance ordering and the zero-results case.

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?

Beyond the schema it clarifies that `query` matches words in title, subtitle or description (the schema only gives examples) and that `category` narrows rather than filters out everything else, plus ties `limit` to the number of matches returned. `limit` itself gets no prose, but its default/min/max are self-explanatory in the schema.

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 first sentence names a specific verb (search), a specific resource (the slopped.site art collection), the exact fields matched (title, subtitle, description), and the optional scoping dimension (category). The no-query fallback ('returns the newest pieces') further pins down the tool's behavior so an agent can distinguish it from get_artwork and from unrelated search siblings like search_world or search_codex.

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?

It gives a clear use case ('find pieces about a subject or mood') and explicitly routes the agent onward with 'follow up with get_artwork for one piece', which is the key alternative. It does not state when NOT to use it or how it differs from the other search_* siblings, so it stops short of full when/when-not guidance.

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