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

With no annotations, the description carries the full behavioral burden. It does valuable work by disclosing the matching algorithm (all words, any order, case-insensitive) and which fields are searched, but says nothing about result shape, ordering defaults, or pagination behavior for what is clearly a paged listing.

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?

A single dense sentence that front-loads the resource and immediately qualifies it with the matching rules. No filler, and every clause adds information an agent needs.

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 4-parameter tool with no output schema and no annotations, the description covers query semantics well but omits pagination behavior and result presentation. It is minimally sufficient, not 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?

Schema coverage is only 25% (only 'sort' is documented). The description adds meaning for the required 'query' parameter by explaining word-matching semantics, but 'page' and 'page_size' remain undocumented in both schema and description, leaving pagination behavior to guesswork.

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 names a specific resource (Decor Depot products) and precisely defines what searching means: matching against title, description, brand, category and attributes. An agent knows exactly what the tool operates on, but the description never distinguishes it from siblings like filter or browse.

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?

There is no statement of when to use search versus the sibling tools 'filter' or 'browse', which are the obvious alternatives for finding products. The matching semantics suggest a keyword-search use case, but routing guidance is entirely absent.

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