run_rakuten_shops_items

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

With no annotations, the description carries the full behavioral burden. It usefully discloses cost ('1 point per returned record') and enumerates the returned fields, but omits read-only confirmation, auth requirements, pagination behavior, and rate limits that would matter for a 500-item-max retrieval call.

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?

A single front-loaded sentence with the purpose first, followed by a short cost note; nothing is padded. The inline field list is dense but serves the reader given there is no output schema.

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 read tool with full schema coverage but no output schema, the description competently compensates by naming the returned fields. Missing items are minor: no mention of pagination behavior (start_page/max_items interplay) or maximum result semantics.

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?

Schema description coverage is 100%, so all three parameters are documented in the schema with examples and bounds. The description adds no parameter detail beyond repeating the shop_code-or-URL input already covered by the schema, so the baseline of 3 applies.

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?

States a specific resource (the item catalog of a Rakuten Ichiba shop) and scopes it by shop_code or URL, so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from siblings like run_rakuten_items or run_rakuten_items_search, so sibling routing is left to inference.

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 never says when to use this tool versus alternatives such as run_rakuten_items_search or run_rakuten_shops, nor does it state any preconditions. It only describes what is returned, leaving the agent to guess at the appropriate context.

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