nex_quote_ip_order

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

No annotations are supplied, so the description carries the full burden. It discloses non-charge ('Nothing is charged'), reservation side effect, catalog-set pricing ('cannot propose an amount'), and return contract ('Returns an intentId'). This is strong behavioral disclosure for a quote/purchase tool.

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?

Three sentences with no filler; every sentence contributes a distinct fact (action, quote side-effect, pricing constraint, return value). Front-loaded with the core purpose. Ideal length.

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 no output schema and no annotations, the description explains what the tool returns, what it does not do (charge), and the downstream step (nex_confirm_ip_order). For a 3-parameter quote tool, this is sufficient for an agent to select and invoke 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?

All three parameters are already fully described in the schema (100% coverage), so baseline is 3. The description adds no parameter-specific meaning beyond the schema; it only relates pricing behavior globally. It does not need to compensate since schema descriptions are adequate.

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?

Description opens with 'Price a proxy IP order and create a short-lived quote' – a specific verb+resource with clear outcome. It distinguishes from sibling nex_confirm_ip_order by noting the returned intentId is passed to it. No ambiguity about what the tool does.

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?

Explicitly states when to use: 'only quote when the user actually intends to buy' and explains the quote reserves the 'single pending-purchase slot.' It frames the workflow by naming nex_confirm_ip_order as the continuation, giving the agent a clear place in the sequence. No alternative tool confusion.

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