Bulk get inventory

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

No annotations are present, and the description provides no behavioral details such as safety, idempotency, rate limits, or return format. The description carries the full burden but offers none, leaving the agent blind to operational characteristics.

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, which is not conciseness but under-specification. It adds no value beyond the title, so it fails to earn its place, though it is not verbose.

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 bulk operation with a nested input array and no output schema, the description is severely incomplete. It does not mention filtering, response shape, error conditions, or any operational context, making it inadequate for an agent to invoke correctly.

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 0% description coverage and the description does not explain what the 'inventories' parameter means, how to structure the array items, or how manageNumber and variantId are used. The nested object structure requires semantic explanation that is entirely absent.

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 a direct Japanese translation of the tool name 'Bulk get inventory' and title, adding no new information. It is a tautology that restates the name without specifying a unique verb or resource beyond what is already obvious.

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 like rms_get_inventory, rms_bulk_get_inventory_range, or rms_get_variant_inventory. No context, prerequisites, or exclusions are provided.

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