redis_del

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

With no annotations, the description must carry the burden of behavioral transparency. It only states 'delete' without mentioning that the operation is irreversible, that non-existent keys are ignored, or that the return value is the number of keys deleted. The output schema may cover this, but the description itself lacks detail.

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?

At 4 words, the description is extremely concise. However, it may be under-specified; a few more words could improve clarity without becoming verbose. It front-loads the essential action but omits helpful context.

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?

Given the tool's low complexity (one required parameter, no annotations), the description is minimally adequate. It covers the core action but lacks information on idempotency, return values, or edge cases. The presence of an output schema partially compensates.

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% for the single parameter 'keys', so the baseline is 3. The description 'List of keys to delete.' adds no extra meaning beyond the schema's description, but it is consistent and correct.

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 'Delete one or more keys' clearly states the action and resource. It distinguishes from sibling tools like redis_hdel (hash field delete) and redis_flushall (delete all keys). However, it does not explicitly differentiate from other deletion tools beyond the resource type.

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 is provided on when to use this tool versus alternatives such as redis_hdel, redis_flushall, or redis_dbsize. The description does not mention any prerequisites, consequences, or comparison with siblings.

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