run_rakuten_shops

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

With no annotations, the description carries the full burden. It usefully discloses a cost trait ('Flat 5 points per successful run') and implies a read-only single-record fetch, but says nothing about failure behavior, auth requirements, or rate limits.

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?

Two compact sentences, front-loaded with the core purpose and return fields, with the cost note trailing. Nothing is wasted, though the field enumeration could be trimmed given no output schema exists to compete with it.

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 single-parameter read tool with no output schema and no annotations, the description covers the input semantics, the returned fields, and the cost model. Only missing element is explicit routing against sibling Rakuten tools, which keeps it out of the top band.

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% and the schema already documents the 'shop' parameter as 'Shop code or URL' with an example. The description's 'by shop_code or URL' repeats that without adding format, validation, or fallback details, 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 verb ('Get') and resource ('one Rakuten Ichiba shop storefront') and enumerates the returned fields, so the agent knows exactly what it retrieves. It doesn't explicitly contrast itself with the many sibling tools like run_rakuten_shops_items or run_rakuten_items, but 'shop storefront' is clearly distinct from item/category tools.

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 by the single-shop scope and the accepted shop_code/URL input, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., run_rakuten_shops_items for a shop's products). The agent must infer routing from the name alone.

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