Get variant inventory

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

No annotations are provided, and the description is just a verb phrase. It does not disclose whether this is a read-only operation, whether specific permissions are needed, what the response contains, or any side effects. The description carries the full burden for behavioral transparency and completely fails to address it.

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 short but this is under-specification rather than concise clarity. It is a single noun phrase with no structure or sentence, and it provides no usable information beyond the tool name.

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?

With no annotations, no output schema, and no parameter descriptions, the description is completely inadequate for a tool with two required parameters. The agent cannot determine how to invoke the tool correctly, what the expected inputs are, or what result to expect.

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 input schema has two required string parameters (variant_id and manage_number) with no descriptions, and the description provides no additional meaning. Schema description coverage is 0%, so the agent has no hint about the expected format, semantics, or relationship between these parameters.

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 'バリアント在庫取得' is just a Japanese translation of the title 'Get variant inventory' and adds no new information. It restates the name/title without explaining what specifically it does or how it differs from sibling tools like rms_get_inventory or rms_bulk_get_inventory.

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 gives no guidance on when to use this tool versus alternatives such as rms_get_inventory or rms_bulk_get_inventory. There is no mention of scenarios, prerequisites, or exclusions, leaving the agent without contextual rationale for selection.

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