Fetch a Kylie Cosmetics page by handle. Returns normalized static page data from the fixed storefront URL.
Get a Kylie Cosmetics static page. Returns normalized static page detail for one Kylie Cosmetics (https://www.kyliecosmetics.com) page handle. The storefront URL is fixed server-side.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | Page handle |
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses that the operation returns normalized data and that the storefront URL is fixed server-side, but it does not describe side effects, response contents, or error behavior. The read-only nature is only implied by '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?
The description is compact and front-loaded with the core purpose. It contains minor repetition of 'Kylie Cosmetics,' but every sentence contributes meaningful 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?
For a one-parameter tool this is mostly adequate, but there is no output schema and the description only vaguely promises 'normalized static page detail.' It also does not guide the agent toward how to discover valid handles or what fields the response will contain.
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 already fully documents the single 'handle' parameter at 100% coverage. The description adds only that it is a Kylie Cosmetics page handle, which is marginal context beyond the schema.
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 starts with a specific verb and resource: 'Get a Kylie Cosmetics static page.' It further clarifies that it returns normalized detail for exactly one page handle, which distinguishes it from listing or product tools.
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 this tool is for fetching a single static page when a handle is known, but it does not explicitly say when to prefer it over kyliecosmetics_pages, kyliecosmetics_product, or similar sibling tools. No alternatives or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.