redis_scan

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

The description adds 'cursor-safe', indicating non-blocking behavior, but does not mention pagination, that results may be partial, or that multiple calls are needed. Minimal transparency beyond that.

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?

Single sentence, no wasted words. Concisely communicates the core function.

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 cursor-based scan tool with no output schema, the description omits critical details: that it returns a cursor for pagination, that it may need multiple calls, or that it returns an array of keys. Incomplete for effective use.

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?

With 0% schema description coverage, the description must explain parameters. It mentions 'glob pattern' (relates to match) and 'cursor-safe' (hints at count), but does not explicitly describe count as a hint for batch size or explain match format.

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 it scans keys by glob pattern using SCAN, specifying the verb 'scan' and resource 'keys'. It distinguishes from siblings like redis_get (single key) and redis_info (server info).

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?

No guidance on when to use this tool vs. alternatives like redis_get for single key retrieval or redis_command for arbitrary commands. Lacks when/when-not usage context.

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