Fetch storefront metadata for Brooklinen's online store from a fixed URL, returning structured store details without requiring any input parameters.
Get Brooklinen store metadata. Returns storefront metadata for Brooklinen (https://www.brooklinen.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 supplied, so the description carries the full behavioral burden. It does disclose one important trait – the server-side fixed URL means no `url` argument exists – but says nothing about authentication, rate limits, or what the metadata contains.
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, zero waste, with the core purpose front-loaded and the parameter constraint appended where it is relevant.
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 storefront lookup with no output schema, the description gives enough to invoke it correctly. It could say a bit more about what "storefront metadata" includes, but nothing needed to make the call is missing.
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?
Zero parameters, so the baseline is 4; the description goes slightly further by explaining why there are none ("no `url` parameter is accepted"), which preempts an agent from attempting to pass one.
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+resource ("Get Brooklinen store metadata") and further pins it to "storefront metadata for Brooklinen" with the domain. This reads distinctly from siblings like brooklinen_products, brooklinen_page, or brooklinen_collections, though it never explicitly says how it differs from them.
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?
Usage is only implied by the resource name – an agent can infer this is the storefront-level metadata call, but there is no explicit when-to-use or when-not-to-use versus brooklinen_page/pages or the other Brooklinen catalog tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.