stevemadden_store

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

With no annotations provided, the description carries the full burden, and it delivers. It discloses the data source (credential-free storefront JSON), the fixed server-side URL constraint, and detailed fallback behavior: if `/products.json` is blocked, it may fall back to a discovered `*.myshopify.com` domain or to embedded page data. This gives an agent a realistic picture of how the tool retrieves data without making assumptions.

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?

Every sentence earns its place. The first states the purpose; the second identifies the source; the third explains the wrapper relationship and parameter constraint; the fourth details fallback behavior. There is no redundancy or filler, and the most important facts are front-loaded.

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?

The tool is simple (zero parameters) and the description covers what it returns, the source, the fixed-URL constraint, and fallback strategies, making it fully invocable. The only minor gap is that it does not enumerate the specific fields contained in the 'normalized storefront metadata,' though no output schema exists; this is a small omission rather than a blocking one.

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?

The input schema is empty, so the baseline is high. The description adds meaningful value by explicitly stating that no `url` parameter is accepted because the storefront URL is pinned server-side, preventing an agent from attempting to pass a URL it might expect based on sibling store tools. This goes beyond the empty schema and addresses a likely point of confusion.

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 opens with a specific verb and resource: 'Get Steve Madden store metadata.' It further clarifies that this is a brand-pinned wrapper around the generic Shopify store family and explicitly notes the storefront URL is fixed server-side, which distinguishes it from generic store tools and other brand-pinned siblings. The resource and scope are unambiguous.

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 effectively positions this tool as the Steve Madden-specific alternative to the generic Shopify store family, explaining that no `url` parameter is accepted because the URL is fixed server-side. This gives clear context on when to use it and implicitly steers agents away from generic tools for this brand, though it does not explicitly name sibling tools or provide explicit when-not-to-use exclusions.

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