iqms_boms_where_used

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

No annotations provided, so description carries full burden. Only states default behavior (single-level). Does not disclose error handling, permissions, or response characteristics. Minimal transparency beyond core function.

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, front-loading the main action. Every word is necessary; no redundancy. Efficient and clear for a simple tool.

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 tool with two parameters and no output schema, the description covers the key purpose and default behavior. Missing details on return format or edge cases, but generally sufficient.

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 50% (only max_level has description). Description reinforces max_level default but adds no new meaning for component_item. Compensates somewhat but could better explain component_item's purpose.

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?

Clearly states finding parent items for a component ('Find every parent item that consumes a given component'). Implies distinction from sibling 'iqms_boms_explode' but does not explicitly differentiate.

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?

Mentions 'Single-level by default', suggesting when to use (single-level) vs. not (multi-level). However, no explicit alternatives or when-not guidance are provided. Sibling 'iqms_boms_explode' likely handles multi-level but is not referenced.

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