delete

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

With no annotations, the description carries full responsibility for transparency. It only states that the tool deletes a key and returns a confirmation or error, without disclosing behaviors like whether it fails on missing keys, side effects, or required permissions. The return type is vaguely described.

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 concise with a clear structure: purpose, arguments, returns. It uses a Python-style docstring format that is easy to parse, though the returns section could be more specific.

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 low complexity of the tool (one parameter), the description covers the basic input and return. However, it lacks details on error handling, typical response formats, and any behavioral nuances that might be helpful for safe invocation.

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 schema has no parameter descriptions (0% coverage), and the description adds only 'The key to delete', which restates the schema's type and name. It provides minimal added value, not explaining what constitutes a valid key or 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 states 'Delete a Redis key', which clearly specifies the verb (delete) and resource (Redis key). It distinguishes from sibling tools like hdel (hash field deletion) and json_del (JSON deletion), though no explicit differentiation is made.

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?

The description provides no guidance on when to use this tool versus alternatives like hdel, srem, or json_del. It does not mention any conditions, prerequisites, or exclusions, leaving the agent to infer usage context from the tool name alone.

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