Retrieve Kylie Cosmetics storefront metadata as clean JSON to inspect store details without passing a URL.
Get Kylie Cosmetics store metadata. Returns storefront metadata for Kylie Cosmetics (https://www.kyliecosmetics.com). The storefront URL is fixed server-side, so no url parameter is accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the storefront URL is fixed server-side and that no url parameter is accepted, which explains the empty schema, but it does not describe what 'metadata' is returned or any read-only guarantee beyond the word 'Get'.
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 short sentences, purpose front-loaded, no filler. The third sentence earns its place by explaining the fixed-URL constraint, though the parenthetical URL is slightly redundant with the tool name.
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, read-only-style metadata tool with no output schema and no annotations, the description is functional but thin: it never says what fields the storefront metadata contains or what a caller can do with it. Adequate as a minimum, but leaves the return content opaque since no output schema compensates.
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 tool takes zero parameters, so the baseline is 4. The description also explicitly justifies the absence of a url parameter, which is a sensible reinforcement of the empty schema rather than a gap.
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 (Get) and resource (Kylie Cosmetics store metadata) with the site identified. It distinguishes itself from other brand tools, but does not clearly differentiate from its own siblings like kyliecosmetics_page/pages or kyliecosmetics_sitemaps, leaving the boundary of 'store' metadata ambiguous.
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?
No statement of when to use this tool versus the numerous kyliecosmetics_* siblings. The only guidance is negative (no url parameter), not a routing cue, so an agent has no basis for choosing this over kyliecosmetics_page or kyliecosmetics_sitemaps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.