List FBS Orders

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

With no annotations, the description must fully disclose behavior. It states it returns order details including buyer info, delivery method, and products. It does not mention pagination behavior, rate limits, authentication needs, or that it's read-only. Adequate but not comprehensive.

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 defines purpose and required/optional filters, second lists statuses and return info. Front-loaded with key information, no wasted words.

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 tool with 7 parameters, 2 required, and no output schema, the description covers the purpose, required filters, status options, and general return content. However, it omits details on pagination (offset/limit), sorting (dir), and warehouse filtering, which are important for a list tool.

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 coverage is 100%, so baseline is 3. The description adds value by emphasizing that date range is required, listing possible status values, and summarizing return content. This goes beyond the schema's individual parameter descriptions.

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 'Get a list of FBS orders (fulfilled from seller warehouse)', with a specific verb ('list') and resource ('FBS orders'), and distinguishes from sibling FBO tools by mentioning 'FBS' and 'seller warehouse'.

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?

It specifies that a date range is required and optional status filtering, including listing possible statuses. However, it does not explicitly guide when to use this tool vs alternatives (e.g., get_fbs_order for single order, list_fbo_orders for FBO), nor does it provide exclusions.

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