Get variant lists

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 of behavioral disclosure. It indicates a read operation but does not explain the meaning of the required parameter, return format, pagination, or any constraints. For a get operation, this is minimal but not completely absent.

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 concise phrase with no wasted words, and it effectively communicates the core purpose. However, it is overly terse because it omits necessary parameter and usage details, but for pure conciseness it scores well.

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 simple tool with one parameter and no output schema, the description is inadequate. It fails to define the parameter, clarify the response, or differentiate from closely related sibling tools (e.g., rms_get_variant_inventory), leaving the description incomplete for reliable invocation.

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?

The schema has one parameter 'manage_number' with zero description coverage, and the description does not mention it at all. The agent is left without any explanation of what manage_number represents or how to use it, so parameter semantics are completely unaddressed.

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 product variant list (inventory)' clearly states a get operation for product variants with inventory data, using a specific verb and resource. It is distinct enough from siblings like rms_get_inventory or rms_get_variant_inventory, though it could be more explicit about the relationship to these tools.

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?

There is no guidance on when to use this tool versus alternatives. The description provides no context about use cases, prerequisites, or preferred scenarios, making the selection decision ambiguous among the many inventory/product tools.

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