get_fba_inventory

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

The word 'Read' implies non-destructiveness, but there are no annotations to confirm. The description lists included data but omits aspects like data freshness, pagination, or scope (all inventory vs filtered).

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?

Single sentence, well-structured, no fluff. Though concise, the misleading content reduces effectiveness.

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?

With no parameters or output schema, the description should clarify the return structure and any limitations. It lists data fields but fails to explain whether the call returns all inventory or requires identifiers. Lacks context relative to sibling tools.

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 has zero parameters, and the description incorrectly implies filtering by SKU/ASIN. This contradicts the schema and confuses parameter usage.

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 it reads FBA inventory levels and lists specific data types. However, it claims filtering 'by SKU/ASIN' yet the input schema has no parameters, creating ambiguity.

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 like get_inventory_health or get_inventory_risk_triage. The agent gets no decision support.

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