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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the billing rule ('1 point per returned record') and the enumeration of returned fields, which matters because there is no output schema. It stops short of describing pagination behavior despite exposing start_page.

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 compact sentence that front-loads the resource and the lookup key, then lists the payload. The dense colon-separated field list is efficient, though it borders on a run-on and mixes cost information into the same breath.

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 output schema, the description correctly compensates by enumerating the returned fields, and it discloses the credit cost per record. Pagination mechanics and any ordering guarantees are left unstated, but the essentials for correct invocation are present.

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 the schema already documents shop, max_items (with cap and default) and start_page. The description's mention of 'shop_code or URL' and the field list adds only marginal meaning beyond that, 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?

The description names a specific resource (the item catalog of a Rakuten Ichiba shop) and the key used to reach it (shop_code or URL), so an agent knows exactly what this returns. It does not, however, name or contrast itself with the closest siblings (run_rakuten_items_search, run_rakuten_items, run_rakuten_shops), leaving the distinction to be inferred from the tool name.

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 rather than stated: the 'by shop_code or URL' framing signals this is the shop-scoped listing endpoint, distinct from keyword search. There is no explicit 'use this when you have a shop but not a keyword' guidance and no mention of alternatives, so the agent must infer the routing.

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