Resolve cached merchant identity, sourced facts, offers, terms, freshness, and safe actions for free. Call this before relying on merchant facts or starting an action.
| Name | Required | Description | Default |
|---|---|---|---|
| client_id | No | Stable, non-secret identifier for the calling client | |
| merchant_url | Yes | Public HTTPS merchant URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this read-only, idempotent, safe, and open-world. The description adds the behavioral trait that data is 'cached' (likely stale) and includes 'freshness' information, which is beyond the annotations and useful for setting expectations. It does not contradict the annotations.
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 two compact sentences, with the main capability front-loaded in the first sentence and usage guidance in the second. No wasted words.
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?
Despite the absence of an output schema, the description lists the types of data returned (identity, facts, offers, terms, freshness, safe actions) and provides a clear use case. It lacks details on return structure or error cases, but for a simple read-only cached lookup, it is adequately complete.
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 provides 100% coverage with descriptions for both parameters ('Stable, non-secret identifier' and 'Public HTTPS merchant URL'), so the description doesn't need to add much. It adds no additional parameter semantics, so the baseline of 3 is appropriate.
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 clearly states a specific verb ('resolve') and lists the exact resources (merchant identity, sourced facts, offers, terms, freshness, safe actions), and notes it is 'cached' and 'free', distinguishing it from likely live-check alternatives among siblings.
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 explicitly says 'Call this before relying on merchant facts or starting an action,' providing clear contextual timing. However, it does not name alternative tools or specify when not to use it, so it lacks explicit exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Clear purpose separation exists among query/search/compare tools, but inspect_merchant is a direct alias for refresh_merchant, and check_merchant, resolve_merchant, and preflight all involve resolving merchant context in ways that could cause misselection. The overlapping inspection/resolution family makes boundaries unclear despite distinct descriptions.
Most tools follow a verb_noun pattern (search_merchants, get_safe_actions, refresh_merchant), but preflight is a single verb with no object and inspect_merchant/refresh_merchant are inconsistent synonyms for the same operation. Otherwise naming is predictable.
Nine tools is within the typical well-scoped range and covers search, inspection, comparison, and action-selection concerns. However, inspect_merchant duplicates refresh_merchant, so the effective tool count is inflated by one redundant alias.
The server covers the core merchant-context lifecycle: cached resolution, paid refresh, search, comparison, safe-action retrieval, and full preflight. Minor gaps exist in documenting what check_merchant adds beyond resolve_merchant, and no explicit execution tool is included, though action execution may be outside scope.
