sellfox_fbm_orders

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

No annotations are provided, so the description must carry the full burden. It only states 'list' without disclosing if the tool is read-only, requires authentication, has rate limits, or behaves in any specific way. The absence of behavioral context is a gap.

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 (4 words in Chinese) but lacks structure. While it is front-loaded, it omits essential details, sacrificing completeness for brevity. It is not efficiently informative.

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 6 parameters, no output schema, and no annotations, the description is far from complete. It does not explain what FBM orders are, how to use the filters, what the response contains, or any other context needed for effective use.

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 100%, providing parameter meanings in Chinese (e.g., '搜索类型' for searchType). The baseline is 3. The description adds no additional context beyond the schema descriptions, so it meets the baseline without improvement.

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 'FBM订单列表' clearly states it is a list of FBM orders, specifying the verb (list) and resource (FBM orders). However, it does not differentiate from the sibling tool 'sellfox_orders' which likely covers all orders, but the purpose is still clear.

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 is provided on when to use this tool versus alternatives like 'sellfox_orders'. There is no mention of prerequisites, filtering context, or exclusions, leaving the agent to infer usage from the name alone.

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