supply_get_down_stream_products

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

No annotations provided, so the description carries full burden. It does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or side effects. The tool is a query, but that is implied rather than stated. The description only says 'query' without clarifying safety or impact.

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 very concise: two sentences for purpose, one parameter description with clear title and explanation. No fluff. Front-loaded with the main action. Every sentence serves a purpose.

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 tool returns downstream products, but there is no output schema and the description does not describe the return format, structure, or example. For a simple query tool, missing this information reduces completeness. Also lacks context on typical use cases or relationship to other 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?

Schema description coverage is 0%, so the description must add meaning. It does: 'keywords: supply chain product keywords, multiple words separated by commas.' This explains the format and intended content. It adds value beyond the schema's type-only information. However, it lacks examples or constraints like max length.

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 the tool's purpose: 'Query downstream product list based on product name.' It specifies the resource (downstream products) and the action (query). The phrase 'product name refers to products involved in the supply chain' adds context. This distinguishes it from sibling 'supply_get_down_stream_enterprises' which focuses on enterprises.

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. The sibling 'supply_get_down_stream_enterprises' is a similar tool, but no comparison or usage context is provided. There is no mention of prerequisites, limitations, or conditions.

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