Retrieve storefront metadata for The Body Shop; no URL parameter is accepted because the endpoint is fixed server-side.
Get The Body Shop store metadata. Returns storefront metadata for The Body Shop (https://www.thebodyshop.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 full burden. It does disclose one genuine behavioral trait beyond the schema: the storefront URL is fixed server-side and no url parameter can be passed. However, it says nothing about response size, authentication needs, or rate limits, which is thin for a tool with zero annotation coverage.
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. The middle sentence ('Returns storefront metadata...') slightly restates the first, but the final sentence about the fixed URL earns its place by explaining the empty schema.
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, no-output-schema metadata tool this is close to sufficient: it names the resource, the fixed URL, and the absence of parameters. It stops short of describing what 'storefront metadata' actually contains (fields, counts), which would close the remaining gap.
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, which is the baseline-4 case per the rubric. The description reinforces this by explaining why no url parameter exists, which is helpful context that the empty schema alone cannot convey.
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 The Body Shop store metadata') and clarifies it is storefront-level metadata for thebodyshop.com. This implicitly distinguishes it from sibling tools like thebodyshop_page, thebodyshop_collections, and thebodyshop_products, though it never names them explicitly.
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 when-to-use guidance and no mention of alternatives among the many thebodyshop_* siblings (pages, collections, products, sitemaps). The agent must infer that this is the root storefront entry point from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.