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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: a 20-result cap, inclusion of source links and last-checked dates, AND semantics across filters, and the caveat that any-store tools are not implied to have native integrations. It stops short of describing result ordering or what happens when no filters are supplied.

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?

Three sentences, zero filler, front-loaded with purpose, then behavioral detail, then the one caveat an agent could otherwise misread. Every sentence carries distinct information.

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?

There is no output schema, yet the description covers the return shape (up to 20 concise matches, source links, last checked dates) and a semantic caveat about result interpretation. Combined with six fully documented parameters and a read-only annotation set, an agent has everything needed to call and interpret this 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 coverage is 100%, so the baseline is 3; the description goes beyond it by stating that filters combine with AND, which is parameter interaction the schema does not express. It does not clarify that all six parameters are optional or what an unfiltered call returns, so it is not exhaustive.

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 (find) and resource (published ecommerce tools) and enumerates the filterable dimensions, so the agent knows exactly what corpus it queries. It is clearly a multi-result search rather than a single-record lookup, but it never names the sibling it is not (e.g. get_tool or compare_tools), so differentiation is inferred from scope rather than stated.

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 description implies usage via the filter list and the 'filters combine with AND' note, which tells the agent how to compose a query, but there is no explicit when-to-use/when-not guidance or named alternative for single-tool or comparison needs. The any-store caveat is useful but is about result interpretation, not tool selection.

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