supply_get_down_stream_enterprises

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

No annotations provided, and the description only explains parameters. It does not disclose whether the operation is read-only, destructive, rate limits, data freshness, or pagination behavior beyond parameter names.

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?

Description is moderately concise with a clear one-liner purpose and a list of parameters. It is front-loaded but could be better structured (e.g., bullet points) for readability.

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?

The description covers only about half of the 18 parameters (missing hasPack, hasStock, etc.) and provides no information about output format or pagination behavior, leaving gaps for a complex query 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?

Though schema coverage is 0%, the description adds significant semantics by explaining parameter details: comma separation for multiple values, allowed values (是/否), address format, date format, and page index starting at 1.

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?

Description clearly states the tool queries a list of downstream enterprises based on product names, distinguishing it from sibling tools like supply_get_down_stream_products which likely query products.

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?

The description lists parameters but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria or usage context. Usage is implied by the resource name.

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