get_order_items

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

The description explicitly starts with 'GET,' which signals a read-only operation, and there are no annotations to rely on. However, it does not describe what the response looks like, whether pagination or filtering behavior applies, or any edge cases. For a simple retrieval tool, the GET method provides a basic behavioral disclosure but nothing more.

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 efficient sentence with no filler. It is front-loaded with the HTTP method and resource path, but it is also terse enough that some necessary detail is missing.

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 three parameters, no annotations, and no output schema, the description is incomplete. It does not explain the two optional parameters, the response format, or any operational context. An agent would not be able to confidently use this tool for non-trivial calls without opening the schema or guessing.

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?

With schema description coverage at 0%, the description must compensate for the undocumented parameters. It only hints that order_id identifies the specific order, leaving status and shop_id unexplained. The description gives minimal added meaning for one parameter and none for the other two.

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 states a clear verb (GET) and resource (order items) and adds the scoping phrase 'for a specific order,' which clarifies that it retrieves items belonging to one order. However, it does not explicitly differentiate it from sibling tools like list_orders or cancel_order_items beyond naming a different resource.

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 about when to use this tool versus alternatives. The description implies it is for retrieving order items, but it does not mention exclusions, prerequisites, or why it should be chosen over list_orders or other related tools.

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