Order detail

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

With no annotations, the description carries the burden of disclosure. It states the tool returns 'full detail JSON', indicating a read operation. However, it does not mention edge cases, return format specifics, or limitations. Given the simplicity of a read-only detail fetch, this is adequate but not rich.

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, front-loaded with the key action and target. No wasted words, and it is appropriately sized for a tool that takes one parameter.

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 is simple: one input parameter and no output schema. The description states the purpose but lacks detail on the response structure and edge cases. Given the simplicity, it is minimally complete, but more detail about the 'full details' would improve completeness.

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 no parameter descriptions (0% coverage). The description clarifies that the parameter is the order number, adding meaning beyond the schema property name. However, it does not explain that the parameter accepts an array of order numbers or any format constraints, leaving the schema to convey that.

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 '注文番号指定で全詳細JSON' clearly indicates the tool retrieves full order details for specified order numbers. It effectively distinguishes itself from siblings like rms_search_orders (search) and rms_get_order_items (items only) by emphasizing 'full detail' and 'order number'.

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?

Usage is implied: use when you have order numbers and need full details. However, it does not explicitly contrast with alternatives or state when not to use it. The context of sibling tools suggests it is for direct order-number lookup, but this is not stated.

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