icboms_procurement_rfq

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.