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

Annotations declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, and the description adds real context beyond them: 'No login' (auth requirement), per-item charging for topCompetitors ('competitor-item'), and 'No extra charge' plus stateful behavior for rankHistoryStore (previousOrganicRank/rankChange/isNew persisted across runs). The destructive hint is implicitly explained by that key-value-store write, though the description never states the write explicitly.

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 sentences plus a compact Actor blurb, front-loaded with the call semantics and immediately followed by the substantive purpose. There is minor redundancy in the boilerplate first sentence, but nothing is padded.

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 an output schema present, return values need no explanation, and the description covers purpose, auth, cost model, and scheduling. The remaining gap is selection guidance against the generic siblings (get-actor-run, get-dataset-items), which the waitSecs/nextStep polling note in the schema partially covers but the description does not reinforce.

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 all 10 parameters, including nested targets and proxyConfiguration, are documented in the schema itself. The description adds no syntax, format, or default information beyond what the schema already provides, so the 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?

The opening sentence is boilerplate ('calls the Actor ... and retrieves its output results'), but the embedded Actor description supplies a concrete verb+resource: tracking product/URL/Smartstore rank in Naver Shopping for Korean keywords, including the data returned (organic rank 1–35, ad slot, price, reviews). That is enough to distinguish it from the other Naver siblings (ai-briefing-monitor, blog-brand-monitor), though the differentiation comes from domain wording rather than an explicit contrast.

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: 'a Naver Shopping scraper built for scheduled rank monitoring' and the rankHistoryStore note 'Run on a schedule to track movement' tell the agent the intended scenario. There is no explicit when-not-to-use and no named alternative among the siblings (e.g. when to poll via get-actor-run instead of calling this tool directly), so guidance stays at the implied level.

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