Retrieve Oh Polly storefront metadata in clean JSON for platform analysis, catalog monitoring, or commerce research without supplying a URL.
Get Oh Polly store metadata. Returns storefront metadata for Oh Polly (https://www.ohpolly.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?
With no annotations, the description must carry behavioral context; it discloses that the storefront URL is fixed server-side and no url parameter is accepted, which is useful. However, it does not state read-only nature explicitly, return format, or any other operational traits beyond the fixed-URL constraint.
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 three short, front-loaded sentences with no wasted words: it states the action, the return, and the key constraint. Every sentence earns its place.
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 metadata tool with no annotations or output schema, the description is nearly sufficient: it says what it does and rules out a URL parameter. It could specify what metadata fields are returned, but the core usage is clear.
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 adds value by explaining the absence of a `url` parameter and why (URL fixed server-side), which clarifies the empty 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 states a specific verb and resource: 'Get Oh Polly store metadata' and 'Returns storefront metadata for Oh Polly', which clearly identifies the tool. It does not explicitly differentiate from Oh Polly siblings like ohpolly_page or ohpolly_products, so it falls 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?
The description implies usage by naming the resource and adding a parameter constraint ('no `url` parameter is accepted'), but it offers no guidance on when to choose this tool over alternatives such as ohpolly_collections or ohpolly_page. Usage is inferable rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.