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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds real value by disclosing the exact shape of the payload (filter specs with type/units/allowed values/importance plus price bands), which is essential since there is no output schema. It stays silent on lookup failure behavior or unknown-intent handling.

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 action and then enumerates the return contract. Every clause earns its place, though the enumeration of filters is slightly list-heavy.

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 dutifully describes the returned contract, which is the main completeness risk for this tool. The remaining gap is sibling disambiguation and the semantics of an unmatched intent.

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 50%: user_signature is thoroughly documented in the schema, while query is bare. The description only indirectly characterizes query as a shopping intent string, adding modest meaning beyond the schema and not compensating for the undocumented parameter.

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?

Clear verb ('Find') plus a specific resource ('Swervie product category') and an explicit statement of what is returned ('its filter contract'). It does not differentiate itself from the sibling browse_category, so the agent must 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?

The phrase 'matches a shopping intent' implies usage (natural-language intent in, category contract out), but there is no explicit when-to-use versus browse_category/get_products/search_products and no stated prerequisites or exclusions.

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