Revuo

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint and openWorldHint. The description adds behavioral context: it's a 'thin call' and specifies the response structure with fields slug, name, description. It does not contradict 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 three sentences, front-loaded with the main action, and every sentence adds value: purpose, relationship to other tools, response format. No redundant 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?

For a simple zero-parameter tool, the description covers all needed context: what it does, output format, and how to use results. Output schema exists externally, so no need to detail return values further.

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 input schema has no parameters, so schema coverage is 100% (vacuously). The description adds no parameter info but explains the response shape. With zero parameters, baseline is 4.

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 verb 'lists' and the resource 'product categories', and explicitly mentions using the returned slugs for filtering in products.search and products.find_by_capability. It distinguishes itself from sibling tool directory.overview by noting it's a 'thin call'.

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 advises when to use this tool (for a thin list) and when to prefer directory.overview (for a full briefing). It also indicates the use of slugs for subsequent product searches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint and openWorldHint, but the description adds valuable behavioral context: it details the exact response structure, the distinction between surfaces and category slugs, and that surfaces are product-bound. No contradictions exist; the description enriches the annotated safety profile.

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 a single, dense paragraph that front-loads the purpose and usage, then provides a structured response summary. Every sentence serves a purpose—scope, timing, content, and a correction—without fluff. It is long but justified for an entry-point tool with substantial output.

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's complexity (extensive return data) and the presence of an output schema, the description nevertheless provides an explicit response shape, clarifies key semantics, and ties to siblings. An agent can confidently call it first and understand the result structure without further lookup. Nothing essential 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?

The tool has zero parameters, so by the rule, the baseline is 4. The description correctly notes 'Parameters: none' and focuses on the output, which is entirely appropriate. No parameter explanations are needed.

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 it is the 'single call this first entry-point' that 'briefs an agent on the entire Revuo directory' and lists exactly what it returns (taxonomy, counts, flags, surfaces, etc.). It distinguishes itself from siblings by naming the subsequent tools it feeds, making its role unambiguous.

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?

Explicitly instructs 'Use this once at the start of a session to ground every subsequent products.search / products.find_by_capability / tools.find_for_task call.' It also clarifies a common pitfall (surfaces are not category slugs), preventing misuse and guiding correct routing to alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds significant detail beyond annotations: explains the return structure, that extension score has evaluated=false for unimplemented checks, and error codes. No contradiction with readOnlyHint and openWorldHint 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 well-structured and concise. It front-loads the purpose, then details parameters and return value in a clear, organized manner. Every sentence adds value without 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 only 3 optional parameters and an output schema, the description is very complete. It explains the return fields, the evaluated=false nuance, and error handling. No gaps.

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 baseline is 3. The description adds value by explaining the mutually exclusive relationship between slug and url, and the effect of refresh. This helps the agent understand parameter semantics.

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 scores an MCP server against a quality rubric, with two distinct modes (slug for cached, url for live). This distinguishes it from all sibling tools which are about listing, searching, or retrieving products/tools/categories.

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?

Explicitly explains when to use slug vs url, including that slug is fast (cached) and url is live. The refresh parameter is also explained. However, no explicit 'when not to use' is given, but the tool is well-scoped.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint and openWorldHint. Description adds detailed behavioral context: pagination with skip/limit, sorting by compositeScore descending, ranking behavior (position and rank within page), and the fact that tier is not a tiebreaker. This goes beyond what annotations provide, making tool behavior transparent.

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 comprehensive but somewhat lengthy. It front-loads the core purpose and then systematically covers calibration, ranking details, and response structure. Every sentence adds value, but the full response schema could potentially be omitted since an output schema is provided. Still, it's well-structured and efficient.

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 complexity (multiple scoring dimensions, pagination, ranking, output schema), the description is thorough. It explains the scoring calibration, ranking behavior, response structure including nested fields like agentReadiness and MCP info. No obvious gaps for an agent to use this tool correctly.

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 covers all three parameters with descriptions. The description adds valuable calibration context for minimumScore (scores 0-100 with thresholds like <30 not agent-ready, 50+ decent, etc.), which significantly enhances parameter understanding beyond the schema's default and range info.

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?

Description clearly states it finds products with highest agent readiness scores, sorted by compositeScore, with pagination. It distinguishes from siblings by specifying the agent-readiness focus and explaining that tier is not a tiebreaker, setting it apart from general search or ranking tools.

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 for finding agent-ready products and provides calibration thresholds for minimumScore, which helps in parameter selection. However, it lacks explicit guidance on when to use this tool versus alternatives like products.search or rankings.get. No 'when not' or alternative tool names are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint and openWorldHint. The description adds detailed behavioral traits: ranking by currentScore then name, paid tier excluded from ranking, position and rank in results, match types (exactSlug, canonicalSlug, nlpFallback). This fully informs the agent of behavior beyond 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 comprehensive and well-structured, starting with purpose then covering ranking, response shape, and empty result handling. It is slightly verbose due to full response detail, but every sentence earns its place given the tool's complexity. Could be trimmed slightly without losing value.

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's complexity (NLP resolution, ranking, varied match types), the description is complete. It covers input handling, ranking logic, response structure (with position/rank), and empty result behavior. The presence of an output schema does not reduce the need for explanation, and the description excels.

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 baseline is 3. The description adds substantial meaning: capability accepts natural language, resolves to structured capability; category scopes search; limit is documented. This exceeds the schema definitions and provides rich semantic context.

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's purpose: 'Find B2B SaaS products that support a specific capability.' It enumerates the types of capabilities (integration, data format, industry standard, compliance) and explains that input can be a canonical slug or natural language with resolution fallback. This specificity differentiates it from siblings like products.search or products.find_agent_ready.

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 implicitly advises when to use the tool (when finding products for a capability) and includes a note that paid tier is not a ranking input. However, it does not explicitly contrast with alternative tools or provide when-not guidance, which would strengthen the dimension.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already include readOnlyHint=true and openWorldHint=true, and the description does not contradict them. It adds valuable behavioral context: agent artifacts are product-bound, knownLimitations carry evidenceUrl to weigh before recommending, and alternatives are neutral with houseProduct disclosed. This exceeds the annotation baseline.

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 long but deliberately structured around the response shape, front-loading the core purpose. Every sentence conveys meaning about fields or interpretation, with no fluff. The length is justified by the complexity of the returned object.

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?

The description completely specifies the response structure, optional fields, edge cases (unverified, verifiedAt absent), error format, and important caveats (knownLimitations, alternatives). For a get-by-slug read operation, nothing essential 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?

The input schema fully documents the sole parameter 'slug' as 'Product slug (URL-friendly identifier)', giving 100% coverage. The description adds no further semantic detail beyond the schema, so it remains at the baseline of 3.

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 precise verb and resource ('Get full details for a product by slug') and enumerates unique content (MCP integration, agent artifacts, readiness scores). It clearly differentiates from sibling search/find tools that operate by criteria rather than a single slug.

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 when to use it: when a specific slug is known and comprehensive product details are needed. However, it does not explicitly contrast with related tools like products.get_mcp_setup or products.find_agent_ready, leaving some routing ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description thoroughly details what the tool returns, including the connect block structure and error cases. It aligns with annotations (readOnlyHint, openWorldHint) and adds useful behavioral context like caching strategies, without contradiction.

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 front-loaded with the main purpose and then provides detailed yet structured information about the response. While somewhat verbose, every sentence adds value given the tool's complexity.

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?

The description covers the input, output schema (including error responses), usage scenarios, and caching advice. It is fully self-contained, leaving no critical gaps for an AI agent to interpret the tool's behavior.

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 coverage is 100% for the single parameter 'slug'. The description repeats the schema's description ('Product slug (URL-friendly identifier)') but does not add new semantic meaning beyond what the schema already provides.

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's purpose: 'Get MCP server setup instructions for a product.' It specifies the exact resource and action, distinguishing it from sibling tools like products.get or products.search by focusing on MCP setup details.

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 provides specific usage guidance, such as how to handle remote vs local servers and mentions caching the hash for drift detection. However, it lacks explicit comparison to sibling tools or conditions when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint. The description adds significant behavioral detail: ranking basis, paid tier not affecting ranking, house product disclosure, unverified flag meaning, error codes, and result attributes. No contradiction with 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 detailed but well-structured: it starts with purpose, then explains fallback, ranking, result fields, and errors. Every sentence adds value, though it could be slightly more concise without losing clarity.

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 complexity of the tool (two search modes, many result fields, error handling), the description is thorough and covers everything needed for correct invocation. The output schema handles return structure, so the description appropriately focuses on semantics and behavior.

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 documented. The description adds value by explaining the query can be a capability slug or natural language, and that category is optional and filters by slug. This goes beyond the schema's basic descriptions.

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 searches for B2B SaaS products by name or capability, with fallback and ranking details. It distinguishes itself from siblings like products.find_by_capability by describing dual search modes, but could explicitly note when to use this vs. that sibling.

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 explains how the tool works (query resolution, fallback, ranking) but does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare to sibling tools like products.find_by_capability.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, but description adds substantial context: ordering basis with published weights, tier not an input, positions never sold, publication schedule, stability, and entry details including houseProduct disclosure. No contradiction.

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?

Description is lengthy but well-structured, each sentence adds value. Front-loaded with purpose and key uniqueness. Could be slightly tighter but efficient for the complexity.

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 output schema exists (implied by detailed response structure in description), the description fully covers return format, errors, and edge cases. Combined with full schema coverage, it is complete for a complex ranking tool.

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 describes both parameters (limit, category) with coverage 100%. Description adds 'caps at 50' for limit and references categories.list for valid slugs, providing useful clarification beyond the 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?

Description uses specific verb 'Get' and resource 'published editorial ranking for a category.' It clearly differentiates from siblings by detailing ordering basis, tier exclusion, and position non-saleability.

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?

Description provides clear context for when to use (get ranking for a category) and references categories.list for valid slugs. However, it does not explicitly state when not to use this tool vs. alternatives like products.search or directory.overview.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, and the description adds detailed behavior: multi-server handling, error codes, response fields like drifted and advice. No contradiction.

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 well-structured with purpose first, then usage, parameters, response. It is somewhat lengthy but each part adds necessary detail for a complex tool. Could be slightly more concise.

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?

With 4 parameters, output schema, and annotations, the description covers all necessary aspects: usage scenarios, multi-server handling, error codes, response fields. No gaps identified.

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%, and the description further clarifies the conditional usage of parameters (EITHER knownHash OR since, server qualification) and the meaning of each, adding value beyond the 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 starts with a specific verb and resource ('Detect whether a product's MCP tool schema has DRIFTED since you cached it'), clearly distinguishing from sibling tools like tools.get or tools.find_for_task by focusing on drift detection.

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?

It explains when to use (before trusting a previously-approved tool) and provides conditional logic for parameters (use knownHash or since, or neither to cache). It does not explicitly mention alternatives among siblings, but the use case is distinct.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint and openWorldHint annotations, describes ranking logic, filtering, result structure, empty case, and preflight annotations in detail.

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?

Long but well-structured, front-loaded with purpose and audience. All sentences are informative, though could be slightly more concise.

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?

With output schema present, description still covers all aspects: ranking, filtering, results shape, empty case, and audience. Very complete for the tool's complexity.

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%, description adds context like default values, filter meanings, and usage hints (e.g., 'Open tools are boosted'). Not all parameters need extra description.

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?

Explicitly states 'Find the best MCP tools for a given task' with detailed explanation. Distinguishes from siblings like products.search and products.find_by_capability.

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?

Provides explicit when-to-use (task description) and when-not-to-use (B2B SaaS recommendations refer to other tools) with alternative tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds behavioral context by detailing the response structure (including fields like normalizedName, displayName, etc., and noting that position and rank are always 1.0) and the error format (with a 'not_found' code). This goes beyond annotations without contradicting them.

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 concise and front-loaded with the primary purpose. It efficiently includes the required parameters, response shape, and error format without extraneous text. Every sentence adds value.

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's simplicity (2 required params, output schema included), the description is complete. Annotations cover read-only and open-world semantics. The description explains the uniqueness constraint, response fields, and possible error. There are no significant gaps for execution.

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 input schema already fully documents both parameters with examples (100% coverage). The description adds value by explaining why both parameters are needed: 'Pass both the productSlug and the tool name — same-named tools across products are distinct.' This clarifies the requirement beyond the schema descriptions.

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's purpose: 'Get detailed information about a specific MCP tool, scoped to one product.' It specifies the verb 'Get' and the resource 'detailed information about a specific MCP tool'. It also explicitly distinguishes this tool from siblings by noting that same-named tools across products are distinct and that both productSlug and tool name are required.

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 when to use this tool: when you have a specific productSlug and tool name to retrieve detailed information. It does not explicitly exclude alternatives like tools.search or tools.list_by_name, but the requirement for exact identifiers and the mention of distinct tools across products provides sufficient guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds significant value beyond annotations: it notes ranking basis (productName), that every result carries position and rank plus preflight annotations, and details the response structure. Annotations already declare readOnlyHint=true and openWorldHint=true, and description complements without contradiction.

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 thorough but not overly verbose. Each sentence adds value, and it is front-loaded with the core purpose. Could be slightly more concise, but structure is effective.

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 that the output schema exists (implied by description of response shape), the description covers all needed aspects: ranking, preflight annotations, and response field details. With one simple parameter and full schema coverage, it is 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 already covers 100% of parameters with a clear description for 'name'. The description reinforces that the name is normalized (e.g., 'search', 'create_issue'), adding slight contextual meaning beyond the 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 explicitly states it 'list every (product, tool) pair that shares a normalized name' with a clear verb 'list' and specific resource. It distinguishes itself as a disambiguation lookup, differentiating from sibling tools like tools.search and tools.get.

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 clearly defines the tool's context: 'a disambiguation lookup — same name across providers does NOT mean the tools are interchangeable.' It also clarifies that paid tier is not a ranking input. However, it does not explicitly state when to use this tool versus alternatives, though the purpose is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=true, and the description adds extensive behavioral details: non-interchangeability of tools across providers, ranking basis, preflight annotations (accessModel, healthScore, etc.), and error handling. No contradiction with 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 detailed but well-structured: it starts with the purpose, then explains result structure, ranking, filters, output schema, and errors. While long, every sentence serves a purpose and there is no redundancy. Could be slightly more concise, but it is efficient for the information conveyed.

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's complexity (4 parameters, output schema, annotations), the description is remarkably complete. It covers ranking logic, preflight annotations for callability, error codes, and how to merge results across tools. The presence of an output schema is noted, but the description still explains the output fields sufficiently.

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 description coverage is 100% (all 4 parameters have descriptions). The description adds context beyond the schema, such as the default for access, the meaning of lexical fallback for ranking, and the effect of remoteOnly. This adds value without redundancy.

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 'Search for MCP tools by capability' and explains each result is a unique (product, tool) pair. It effectively distinguishes from sibling tools like tools.list_by_name or products.search by focusing on capability-based semantic search.

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 provides explicit when-to-use context (search by capability) and explains the ranking behavior (semantic vs lexical fallback). It mentions optional filters (access, remoteOnly) but does not explicitly state when not to use this tool versus alternatives. However, the sibling context and clarity make it adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.