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

With no annotations, the description carries the full burden. It usefully discloses matching semantics (exact, case-insensitive, keys are the store's own spec attributes) and the currency unit for prices, but says nothing about pagination behavior, default sort, result shape, or limits despite page/page_size/sort parameters existing.

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 primary behavior. The parentheticals are information-bearing rather than filler, though the sentence crams a lot together and could be split for scanability.

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 10-parameter tool with a nested attributes object and no output schema, the description covers the core filtering semantics adequately but omits pagination, sort ordering, and result-shape guidance, leaving meaningful gaps an agent would need to guess at.

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 only 30%, so the description has to compensate. It does add real meaning for the confusing params — attributes (key:value, exact, case-insensitive, store-specific keys) and price units (major units of Dresser House's currency, with 200/1500 examples) — but page, page_size, sort and fulfilment remain unexplained in both places.

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 states a clear verb (filter) and resource (Dresser House products) and specifies the two filter axes — attribute key/value matching and a price range. It does not, however, distinguish this tool from siblings like search or browse, leaving the agent to infer the boundary.

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 hints at composition ('Combine with a category, brand and in-stock') which implies intended usage, but never states when to reach for filter versus search or browse, and offers no exclusions or alternative routing.

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