get_awd_inventory

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

With no annotations, the description carries full burden. It clearly notes the tool is a stub locally and is a read operation. This honesty about its limited functionality is valuable, though it could elaborate on what happens when called.

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 concise sentences: first presents purpose, second notes the limitation. Every word contributes, and the most critical information is front-loaded.

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 read tool with no output schema, the description covers the resource and its limitation. It lacks details on return format or pagination, but given the stub context, it is reasonably complete.

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 input schema has 100% parameter coverage with descriptions. The tool description adds no extra meaning beyond 'AWD inbound and on-hand stock', so it meets the baseline without further value.

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 'AWD inbound and on-hand stock', specifying the exact resource this tool accesses. The category '[Inventory / read]' further clarifies verb and domain, distinguishing it from sibling tools like get_fba_inventory or get_inventory_health.

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 mentions 'Hosted endpoint only; this local stdio server is an introspection stub', implying it is not functional locally. However, it does not explicitly state when to use this tool versus alternatives or provide any scenario guidance.

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