Fetch Fashionphile storefront metadata for structured store details. The URL is fixed server-side, so no URL parameter is accepted.
Get Fashionphile store metadata. Returns storefront metadata for Fashionphile (https://www.fashionphile.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.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose a genuine behavioral trait — the storefront URL is fixed server-side — which usefully explains why the tool takes no arguments. However, it says nothing about permissions, rate limits, or whether the call is read-only, leaving gaps for an unannotated tool.
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, front-loaded with the purpose. It is slightly redundant, restating 'store metadata' as 'storefront metadata for Fashionphile,' but nothing is bloated or wasted.
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-param, no-output-schema metadata call, the description covers what the tool is and why it takes no arguments. It does not hint at what metadata fields are returned, which is the main remaining gap given there is no output schema to document the response.
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 has zero parameters, so the baseline is 4. The description sensibly explains the absence of a url parameter ('fixed server-side, so no url parameter is accepted'), preempting an obvious expectation.
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 ('Fashionphile store metadata'), making it clear this returns storefront-level metadata rather than products or collections. It does not explicitly differentiate itself from nearby siblings like fashionphile_page or fashionphile_pages, so it stops short of a 5.
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?
There is no guidance on when to use this tool versus the other Fashionphile siblings (products, collections, pages, search). The only conditional information is that no url parameter is accepted, which is a constraint rather than usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.