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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds useful context beyond that with 'Public' (no auth needed) and the shape of what is returned (price and buy link where set). It stops short of describing pagination or list size.

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 dense sentence, front-loaded with the 'Public' access qualifier and ending with the actionable route to rokha_addon_add. Minimal waste, though the parenthetical tag detail is slightly buried.

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 zero-param read-only catalog, annotations carry the safety profile and the description conveys scope, access level, and returned fields. No output schema exists, but the description names the payload elements (price, buy link), leaving little an agent would need before calling.

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?

The tool takes zero parameters, so the schema/description carry no argument semantics to explain. Baseline for a zero-param tool is 4; nothing is missing that an agent would need.

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+resource: it is the shelf of published rigs and skills tagged rokha-addon, with price and buy link. This clearly separates it from rokha_addon_add/remove (attach/detach actions), though it does not explicitly distinguish itself from the similarly named rokha_addons sibling.

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?

Names the follow-up action explicitly ('Attach one with rokha_addon_add'), giving the agent a clear next step and implicit routing away from the mutation siblings. It does not state when-not-to-use it or contrast with rokha_addons, but the primary context is clear.

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