scan_next

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

Without annotations, the description discloses it narrows the scan and uses a scan_type vocabulary. However, it does not mention required state (active scan), side effects, or error conditions, leaving gaps in behavioral understanding.

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 concise sentences: the first defines purpose, the second gives typical usage with examples. No extraneous text.

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?

Despite having 3 parameters and no annotations or output schema, the description fails to explain prerequisites (active scan), parameter details for value and value2, or return behavior, leaving the tool under-specified.

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 coverage is 0%, and the description only explains scan_type. The parameters value and value2 are not described, and their roles (e.g., comparators for narrowed scans) are only vaguely implied by the typical usage example.

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 clearly states that the tool narrows an active scan and references scan_first for vocabulary. It distinguishes itself as the next step after an initial scan, differentiating from siblings like scan_first and scan_reset.

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 typical usage: scanning changed/unchanged/increased/decreased while in-game value moves. Implicitly indicates use after an initial scan, but does not explicitly state when not to use or alternative tools.

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