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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds useful context beyond them: the 'Members only' authorization requirement and a breakdown of what the response contains (counts, per-variant stock, waiting orders, oversold units).

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 core resource and its contents are front-loaded in the first two sentences, and the prerequisite follows. There is mild filler ('so the seller knows what the shelf does not cover', 'as facts an agent can act on') that does not add actionable information, keeping it from a 5.

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 carries the return-value burden and does so by enumerating the aggregate fields returned. Combined with annotations covering the safety profile and a documented 'Members only' constraint, an agent has enough to invoke it correctly; only pagination/size expectations are unaddressed.

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 both parameters (projectId, includeArchived) are already documented by the schema. The description alludes to archived counts implicitly but adds no syntax, defaults, or format detail beyond what the schema provides; baseline 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 ('Inventory overview for a rikma') and enumerates exactly what it aggregates: active/archived/low/out-of-stock counts, per-variant stock, waiting orders, and oversold units. This differentiates it from the list-style siblings (listRikmaProductsTool, listRikmaProductVariantsTool) because it returns aggregate counts rather than item lists.

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?

Provides a prerequisite ('Members only') and a real-world anchor ('what the Stock tab of sales/manage shows'), which implies when the tool is relevant. However, it never states when to prefer this over listRikmaProductsTool or its write counterpart setShopStockTool, so routing between siblings is left to inference.

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