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

With no annotations, the description carries the behavioral burden and does convey the core behavior: comparing specifications and checking for pin-to-pin or drop-in alternates. However, it does not disclose what the response contains, how alternates are determined, or error behavior, which are meaningful gaps given there is no output schema.

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 with no filler. Every clause contributes useful information: the operation, the target, the check being performed, and the cardinality constraint.

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 one-parameter comparison tool, the description covers the core purpose and input scope well. However, with no output schema, it should still clarify what the tool returns or how results are presented; it also does not mention how this tool relates to sibling tools, so some context remains 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?

Schema description coverage is 100%, so the mpns parameter is already well documented with type, range, and an example. The description adds domain context ('electronic components,' 'alternates') but no additional parameter semantics or format details, so the 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 identifies a specific operation ('Compare'), a concrete target ('parametric specifications'), and additional outputs ('pin-to-pin or drop-in alternates'), while explicitly limiting scope to 2–8 electronic components. This clearly distinguishes the tool from siblings like search, product facts, and procurement.

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 implies when to use the tool: when comparing multiple components or checking interchangeability. It does not explicitly state when not to use it or name alternatives, but the context is strong enough for an agent to route correctly.

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?

No annotations are provided, so the description carries the burden. It indicates the tool returns verified data from ICBOMS, which is a useful behavioral clue, but it does not mention read-only behavior, not-found handling, or data freshness. There is no contradiction with structured metadata.

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?

A single, front-loaded sentence conveys the tool's output categories and input scope with no filler. 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?

For a simple one-parameter lookup with no output schema, the description adequately names the return content (specs, package, manufacturer, lifecycle) and source. It could add optional notes on error behavior or data coverage, but nothing critical is missing for an agent to invoke it 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?

The input schema already documents the single parameter `mpn` with examples at 100% coverage. The description adds little beyond restating that it operates on a specific MPN, 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 uses a specific verb ('Get') and concrete resource scope: verified electrical specs, package information, manufacturer, and lifecycle facts for a given MPN from ICBOMS. This clearly separates the tool from siblings like search, compare, and RFQ, whose purposes are distinct.

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?

Usage context is implied: call this when you already have a specific MPN and need product facts. However, there is no explicit guidance about when to prefer search_components or compare_parts instead, and no exclusions or preconditions are stated.

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?

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions Shenzhen stock verification and international DDP delivery instructions, but it does not explain whether this is a read-only lookup, whether it triggers a quote creation, what happens on insufficient stock, or what the output looks like. The behavior is therefore only partially 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 a single sentence with no fluff, and the action verb 'Get' is front-loaded. It conveys the general scope quickly. However, the list-like construction 'procurement, ... verification, ... instructions' is slightly awkward and could be phrased more clearly.

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?

There is no output schema, so the description should clarify what the agent will actually receive. It lists three vague outputs but does not specify their format, whether prices are included, how destination_country affects the result, or why target_price_usd matters. For a tool of this complexity, the description is incomplete.

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%, with both bom_lines and destination_country having descriptive text in the schema. The tool description itself does not add parameter-specific meaning beyond the schema. It gives context about procurement and DDP but not about how the parameters interact, so the 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 a specific verb 'Get' and names a clear domain resource: 'turnkey BOM procurement' plus associated services. It is distinguishable from siblings like icboms_search_components and icboms_compare_parts, which clearly belong to different concerns. However, the phrasing is a bit ambiguous because it lists three separate outputs rather than stating what the tool actually returns.

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?

There is no guidance on when to use this tool versus alternatives such as icboms_search_components or icboms_compare_parts. No context, exclusions, or conditions are provided. The only clue is the tool's name and domain-specific wording, which is not enough for confident selection.

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 provided, the description must disclose behavioral traits itself, but it only states the search action without revealing whether the operation is read-only, what the return format is, or any side effects. For a search tool, the absence of any statement about non-mutating behavior or result handling leaves the agent without critical operational context.

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 action and resource, then specifies the search criteria. There is zero redundancy or filler. Every word contributes to the core purpose, making it highly scannable for an agent.

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 2-parameter search tool with no output schema and no annotations, the description gives the essential purpose but omits any indication of result shape, pagination, or behavior when no matches are found. While not as critical as for a mutation tool, the absence of these details prevents the agent from fully anticipating the tool's response, especially given the lack of an output_schema to compensate.

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%, so both query and limit are documented in the schema. The description's phrase 'by MPN or keyword' mirrors the query schema description and adds no additional semantics. It does not explain limit behavior beyond what the schema already states (e.g., max, default). Since coverage is high, the baseline 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 states a specific verb ('Search') and resource ('electronic components... across the ICBOMS catalog') with precise categories (microcontrollers, semiconductors, passives) and search criteria (MPN or keyword). This unambiguously distinguishes it from sibling tools like icboms_get_product_facts (retrieve facts) and icboms_compare_parts (comparison), 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 when to use this tool (any time you need to find components by MPN or keyword), but it does not explicitly contrast with sibling tools or mention prerequisites. No exclusions or alternative rounting are provided, leaving the agent to infer the boundary between searching and subsequent actions like retrieving facts or comparing.

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