Fetch one full structured comparison (items with scores, sub-scores, per-criterion values, badges, sources, sourced/estimate flags, freshness). Neutral ranking, never paid. Data is localized to the requested lang/country.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | 2-letter language code. Default: en. | |
| slug | Yes | Comparison slug (from search_comparisons). | |
| country | No | 2-letter country code. Default: US. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the detailed response contents, neutrality policy, and localization behavior. It does not mention error handling or data freshness specifics, but for a straightforward read operation, the disclosure is adequate.
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 sentences, front-loaded with the primary action and a detailed list of returned data. Every sentence adds value: the first specifies the tool's output and scope, the second conveys policy and localization. No filler or redundancy.
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?
Given the tool has 3 parameters, no output schema, and no annotations, the description provides a solid overview of what is returned and the localization behavior. It lacks explicit error conditions or response format details, but for a single-item fetch tool, the description is reasonably 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?
Schema coverage is 100%, so parameters are well-documented in the schema. The description adds value by explicitly connecting lang/country to localization and clarifying that slug is from search_comparisons, enhancing the semantic meaning beyond the raw 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 clearly states the tool fetches one full structured comparison, enumerating the contents (scores, sub-scores, per-criterion values, badges, sources, flags, freshness). This distinguishes it from siblings like search_comparisons (searching) and list_categories (listing categories), making the purpose unmistakable.
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 context by mentioning the slug comes from search_comparisons, indicating this tool is for retrieving a specific comparison after searching. It also adds a usage caveat (neutral ranking, never paid) but does not explicitly state when not to use it or provide exclusions.
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.
Each tool has a distinct role: listing categories for browsing, searching to find comparisons, and fetching a full comparison by slug. There is no overlap in purpose, and the descriptions clearly separate discovery from retrieval.
All tool names follow a consistent verb_noun pattern: list_categories, search_comparisons, get_comparison. This predictable naming makes the tool's function immediately apparent.
With three tools, the set is minimal but covers the core workflow of exploring and retrieving comparisons. It is slightly lean for a full-featured catalog but not under-scoped for a read-only API.
The tools enable browsing categories, searching, and fetching details, which covers the primary use case. However, there is no direct way to list all comparisons within a category, which could be a minor gap depending on how search filters work.