delete

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

No annotations are provided, so the description carries full behavioral disclosure burden. It mentions deletion but lacks key behavioral traits: whether the key must exist, if deletion is irreversible, error specifics (only 'error message' is vague), or side effects. The destructive nature is implied but not elaborated.

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?

The description is very concise, using only four lines to state purpose, parameters, and return. It is front-loaded with the action and well-structured with Args and Returns sections. However, the brevity sacrifices informative content.

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 simplicity (1 param, no annotations, output schema exists), the description adequately covers the basic operation and return type (confirmation or error). However, it does not address edge cases like non-existent keys or complex key types, and it does not explain the output structure beyond a string. Sibling tool complexity suggests more context would be beneficial.

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?

The input schema has one required parameter 'key' with no description (0% schema coverage). The description merely repeats 'key (str): The key to delete,' adding no additional meaning about format, constraints, or valid values. It fails to enrich understanding beyond the schema.

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 'Delete a Redis key,' specifying the action and resource. The tool name 'delete' is generic, but naming it as a Redis key deletion helps distinguish it from sibling tools like 'hdel' or 'srem' that delete specific data structure elements. However, it does not explicitly differentiate from other delete operations.

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. With many sibling tools for different data structure deletions (e.g., hdel, lrem, zrem), the description should indicate that this tool is for top-level key deletion, not for fields or members. The absence of usage context hinders correct selection.

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