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

Annotations already declare readOnlyHint and openWorldHint, and the description adds a real behavioral trait beyond them: best-effort relevance matching that can return the storefront's fallback recommendations instead of an empty result. This is genuinely useful for interpreting surprising results, though return format and pagination behavior are not covered.

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?

Two sentences, front-loaded with the core action and followed by the important fallback caveat. The midsentence parenthetical is a bit dense but each clause earns its place; nothing is redundant.

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?

An output schema exists, so return-value description is unnecessary, and the description covers storefront selection plus fallback behavior. The main gap is that pagination and the page parameter are never addressed, but overall this is sufficient for correct invocation.

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 0%, so the description must compensate. It clarifies the brand parameter's role and default (Old Navy) and implies keyword behavior, but 'page' is entirely unexplained and brand lacks enumerated values despite four valid storefronts being named.

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 (Search) and resource (product listings), and extends scope to four named brand storefronts rather than just Old Navy. This clearly distinguishes it from siblings like oldnavy_product, oldnavy_categories, and oldnavy_category.

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 tells the agent how to pick a storefront via the brand field (default Old Navy), which is genuine selection guidance. However, it never routes the agent away from this tool to a sibling (e.g., oldnavy_product for detail lookups or oldnavy_categories for browsing), so when-not-to-use is left implicit.

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