get_inventory

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

No annotations provided; the description only states real-time stock but does not disclose any behavioral traits such as data freshness, rate limits, error handling, or what happens if the SKU is missing. The agent gains no insight beyond the basic 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?

The description is extremely concise (one short phrase) but lacks structure and sufficient information. Brevity is not beneficial when essential details are omitted. It should at least include a sentence about usage context.

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?

Given the tool has 2 parameters, no schema descriptions, no annotations, and an output schema (which is not described), the description provides minimal context. It does not explain the return format, pagination, or any constraints, leaving the agent poorly informed.

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?

With 0% schema description coverage, the description must compensate but only mentions 'by SKU,' ignoring the marketplace parameter. It does not explain the purpose, allowed values, or format of the parameters, leaving the agent uncertain about what to provide.

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 the tool retrieves real-time FBA stock by SKU. It specifies the verb (get stock) and resource (FBA inventory). However, it does not differentiate from sibling tools like get_fba_inventory, which may have overlapping functionality.

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 on when to use this tool versus alternatives such as get_fba_inventory or others. The description does not specify prerequisites, required permissions, or context for when this tool is appropriate.

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