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

No annotations are provided, so the description carries the burden. It discloses supported networks (Awin, Amazon, Tradedoubler) and implicitly suggests auto-detection, but does not mention output format, authentication requirements, rate limits, or error behavior for unsupported URLs. This is moderate transparency for a simple utility.

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 sentence that front-loads the primary action and includes essential scope (supported networks). No filler, perfectly 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?

The tool has no output schema, so the description should explain what the tool returns or at least hint at the output. It does not. It also lacks details on unsupported URL handling or failure modes. While the tool is simple, missing return value and error context makes it incomplete for an agent.

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 provides full descriptions for both parameters (url and network), with 100% coverage. The description adds no extra parameter-level information, so baseline score 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 uses specific verb 'Convert' and resource 'regular product URL into an affiliate tracking link', clearly distinguishing it from sibling tools like search_products or list_merchants. It also names supported networks, adding precision.

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 states the tool's purpose, making it obvious when to use it (when you have a product URL and need an affiliate link). However, it does not mention alternatives or explicit exclusions, so it falls short of a 5.

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?

With no annotations, the description carries the burden of disclosing safety and behavior. It implicitly signals a read-only operation ('List') but does not mention authentication, pagination, or potential errors. For a simple listing tool, this is adequate but not rich.

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, front-loaded sentence that clearly states the purpose and key output fields. There is no wasted wording or unnecessary detail.

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 lists the main output fields (networks, commission rates, feed status), which is sufficient for a simple list tool with no output schema. It could mention pagination or ordering, but 'all configured' implies a full list, making it 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?

The tool has zero parameters, and the schema coverage is 100% by default. The description does not need to explain any parameter details, aligning with the baseline of 4 for parameter-free tools.

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 function: 'List all configured affiliate merchants' with specific details (networks, commission rates, feed status). This distinguishes it from sibling tools like search_products or generate_affiliate_link, which perform different operations.

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 clear context that this tool retrieves the full merchant list. While it doesn't explicitly mention when not to use it, the sibling tools are all action-oriented (search, match, generate, sync), leaving no ambiguity about when a list operation is needed.

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?

With no annotations, the description carries the full burden. It discloses the primary behavior (returns best matches with prices and affiliate links) but lacks details on edge cases like no matches found, partial matching, or any side effects. This is adequate but not deeply 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?

Two sentences fully convey the tool's purpose and output with zero filler. The structure is front-loaded with the action and resource, making it efficient for an agent to parse.

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 lacking an output schema, the description provides a high-level summary of the return format (best matches, prices, affiliate links). It covers the essential context for a matching tool, though it could detail what 'best match' means or how multiple networks are handled.

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 covers 100% of parameter descriptions, so the baseline is 3. The description adds marginal value by reinforcing that items are a list of components/parts and that output includes prices and links, but it does not clarify network or marketplace specifics 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 clearly states the tool's function: matching a Bill of Materials against affiliate product catalogs and returning best matches with prices and links. The verb 'Match' and resource 'Bill of Materials' distinguish it from sibling tools like search_products, which likely handles single product queries.

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 phrase 'Ideal for project material lists' provides clear context for when to use this tool. It implies multi-item input scenarios but does not explicitly mention when not to use it or alternatives, which would earn a 5.

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?

With no annotations, the description carries the full burden for behavioral disclosure. It states that the tool searches across multiple networks and returns products with prices and affiliate links, which is useful. However, it does not disclose any other behavioral traits such as rate limits, failure handling, or whether results are merged from all networks simultaneously. The description is adequate but not overly informative.

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, concise sentence that front-loads the main action and return type. There is no redundant information or filler, making it highly efficient and easy to parse.

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 schema fully documents all parameters, the description only needs to convey the tool's purpose and return type, which it does. The absence of an output schema is partially mitigated by the clear statement that it returns products with prices and affiliate links. However, it could have benefited from mentioning the availability of filters like networks, merchants, and max_results, though these are covered in the schema.

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 provides 100% coverage with detailed descriptions for all 5 parameters, including defaults and constraints. The description does not add any additional parameter semantics beyond what the schema already offers, so the baseline score of 3 applies.

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 action ('Search for products'), the resource ('products across affiliate networks'), and the specific networks (Awin, Amazon, Tradedoubler, AliExpress). It also identifies the return value ('products with prices and affiliate links'), which distinguishes it from sibling tools like match_bom, generate_affiliate_link, list_merchants, and sync_feeds that perform different functions.

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 that this tool is used to search for products across the listed affiliate networks, but it does not explicitly state when to use this tool versus alternatives like match_bom or generate_affiliate_link. There is no mention of when not to use it or any alternative guidance, leaving the usage to be inferred from the name and purpose.

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?

With no annotations, the description carries the full burden. It states that the tool downloads and updates product feeds and refreshes the local DB, which reveals its primary effect. However, it does not disclose potential side effects such as overwriting local changes, resource consumption, or failure behavior. This is adequate but not deeply 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?

Two sentences, no redundancy. The first states the action and sources, the second clarifies the purpose and when to run it. Every word 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?

Given the simple tool shape (2 optional params, no output schema, clear siblings), the description provides all necessary high-level context: what it does, what data it touches, and when to run it. The schema fills in parameter specifics. No significant 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?

The schema covers 100% of parameters with clear descriptions for 'force' and 'merchants'. The description adds no additional parameter information beyond what the schema already provides, matching the baseline for high schema coverage.

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 uses specific verbs ('Download and update') and names the exact resources ('product feeds from Awin and Tradedoubler') and the purpose ('refresh the local product database'). This clearly distinguishes it from siblings like search_products, match_bom, generate_affiliate_link, and list_merchants.

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 phrase 'Run this to refresh the local product database' provides clear context for when to invoke this tool. It implies it is the go-to tool for updating local data before searching or matching, but it does not explicitly name alternatives or exclusion criteria, which would warrant a 5.

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