iqms_navigate

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Navigate to ... to see its tools' without mentioning whether the operation is read-only, has side effects, requires permissions, or what the response contains. This is insufficient for an agent to understand the tool's behavior.

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 well-structured, listing domains in a clear format. It front-loads the purpose and then provides domain details. No unnecessary sentences.

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 navigator tool with one parameter, the description is adequate but incomplete. It does not specify what 'see its tools' means in practice (e.g., does it return a list of tools, change context, etc.). No output schema is provided, so the description should clarify the expected result.

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 already provides an enum for domain with descriptions, but the tool description adds significant value by explaining what tools each domain contains (e.g., 'workorders: list/get work orders, post production'). This helps the agent understand the meaning of each domain beyond a simple label.

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 'Navigate to an IQMS domain to see its tools,' specifying a verb (navigate) and resource (domain). It distinguishes from sibling tools which are specific operations (e.g., iqms_boms_explode, iqms_inventory_onhand), making the purpose 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?

The description lists domain options with brief tool descriptions, implying when to use each domain. However, it does not explicitly state when to use this tool over alternatives, such as when to navigate vs using a specific tool directly.

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