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

With no annotations, the description carries full burden. It discloses the return data (SKUs, quantities, conditions) and the prerequisite. However, it lacks details on pagination behavior, filtering logic (e.g., how search works), and rate limits. Adequate but not thorough.

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 concise sentences: first states purpose, second gives usage guidance, third mentions prerequisite. No redundancy, well 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?

Given four parameters and no output schema or annotations, the description provides basic purpose and usage but omits parameter explanations and output structure. Adequate for a simple tool but leaves gaps for effective agent invocation.

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 does not explain any parameter (page, limit, search, min_quantity). The parameter names are self-explanatory, but the description fails to add meaning beyond them, leaving agents to infer 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 returns live FBA inventory with SKUs, quantities, and conditions. It specifies when to call (user asks about stock or specific SKU), distinguishing it from sibling tools like get_amazon_orders or get_aged_stock.

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?

Provides explicit when-to-call guidance ('Call when the user asks what stock they have or about a specific SKU/product they sell') and a prerequisite ('Requires their Amazon account to be connected'). No explicit exclusions or alternative tools mentioned, but context is clear.

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