Run Read-Only Redis Command

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description reinforces this while adding a useful guardrail: write commands and KEYS are refused. It does not discuss return/error behavior in detail, but for a read-only command runner the safety-relevant behavior is disclosed.

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 tight sentences: the core action is front-loaded, followed by concrete examples and a crisp exclusion. There is no filler, redundancy, or unnecessary restatement.

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 generic Redis command runner, the allowed-command examples and refusal rule give enough context to select and invoke it correctly, and the schema covers all parameters. It would be slightly stronger with a note about raw return shape or command errors, but the definition is still sufficient without it.

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 command, args, and database are already documented structurally. The description's command examples help set expectations, but it adds little parameter-level meaning beyond what the schema already provides.

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 opens with a specific action and resource: 'Run one read-only Redis command', and lists representative commands like GET, HGETALL, LRANGE, and SCAN. It is immediately distinct from the sibling SQL/query tools, and the refusal of write commands and KEYS further pins down its scope.

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?

It clearly states when to use the tool: for read-only Redis commands. It also explicitly gives a when-not signal by refusing write commands and KEYS. It does not name alternative tools for those cases, so it falls just short of full 5-level guidance.

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