orders_GetInventory

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

With no annotations, the description carries the full behavioral burden and mostly does not meet it: it does not confirm whether the call is read-only, whether authentication or a service session is required, or what happens on an unknown SKU. The 'Get' prefix weakly implies a read, which is the only behavioral signal present.

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?

Very short and front-loaded, so it is not verbose, but the one sentence spends its words on adapter/service plumbing ('adapter: orders') rather than information the agent can act on.

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?

No output schema exists, so the description should say what inventory data comes back, and it does not. For a lookup tool with an undocumented parameter and no annotations, the definition leaves the agent guessing on both input format and return shape.

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 0% and the description says nothing about the single required 'sku' parameter — no format, casing, or example. The parameter name is largely self-explanatory, so this is not fully opaque, but the description adds zero meaning beyond the schema.

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 is essentially a restatement of the operation name plus adapter metadata: 'SOAP operation GetInventory on service Orders.' It conveys that inventory is retrieved, but never says what inventory means (stock levels, availability, warehouse counts) or how it differs from orders_GetOrder / orders_ListOrders beyond the name.

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?

No guidance at all on when to call this versus the sibling order tools, and no preconditions or exclusions are stated. The agent must infer usage purely from the operation name.

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