bos_product_variants

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

The description lacks any behavioral context beyond a simple retrieval. It does not disclose if the tool returns all variants at once or paginated, whether it requires authentication, or any side effects. Annotations are absent, so the description carries full burden, but fails to inform.

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 a single, clear sentence with no extraneous words, achieving conciseness. However, it lacks any structured breakdown (e.g., separating purpose from usage notes).

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 no output schema and only one parameter, the description is incomplete. It does not explain what a 'variant' is, the return structure, or any constraints like result limits, which are critical for a tool of this complexity.

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 0%, meaning the product_id parameter has no description in the schema. The description does not add any meaning (e.g., format, example) to help the agent understand what constitutes a valid product_id.

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 'Get all variants for a product' uses a specific verb ('Get') and resource ('variants for a product'), clearly distinguishing it from siblings like bos_product_show (which shows product details) and bos_product_list (which lists 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?

No guidance is provided on when to use this tool vs alternatives, such as when to retrieve product details vs. variants, or any prerequisites like the product existing.

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