kyliecosmetics_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 excels: it discloses the credential-free data source, normalization behavior, the fixed-server-side URL constraint, and a detailed fallback chain (vanity domain → discovered `*.myshopify.com` → embedded page data) when `/products.json` is blocked. This is rich behavioral context beyond what any annotation could have 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?

Purpose is front-loaded in the first sentence, followed by data source and behavioral detail. The only waste is a slight redundancy between 'Get Kylie Cosmetics store metadata' and 'Returns normalized storefront metadata for Kylie Cosmetics' in consecutive sentences; otherwise every clause earns its place, including the fallback nuance.

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 zero-parameter tool with no annotations and no output schema, the description is nearly complete: it covers purpose, source, auth posture, parameter surface, and fallback behavior. The only gap is that 'normalized storefront metadata' doesn't hint at what fields the agent will receive, and with no output schema the description could have named a few (name, domain, currency) to support downstream planning.

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 schema is an empty object, and the description adds crucial meaning by explaining why there are no parameters: the URL is fixed server-side and no `url` parameter is accepted. This preempts the natural agent question of how to specify the store and distinguishes this wrapper from the parameterized generic `shopify_store`. For a 0-param tool, this exceeds the baseline.

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 and resource ('Get Kylie Cosmetics store metadata') with the exact storefront URL, and explicitly differentiates itself as a 'brand-pinned wrapper around the generic Shopify store family' — distinguishing it from both generic `shopify_store` and sibling brand-pinned stores like `skims_store` or `allbirds_store`. Also distinguishes from the kyliecosmetics_products/collections/pages siblings by scoping to store metadata.

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?

Provides clear selection context by positioning the tool within the Shopify store family and explaining that the storefront URL is fixed server-side, so no `url` parameter is accepted — which tells an agent it cannot and need not parameterize this call. However, it never explicitly names a sibling alternative (e.g., 'use shopify_store for other stores') or states a when-not-to-use condition, so it stops short of a 5.

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