storage_cleanup

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

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It says 'Remove keys,' implying a destructive operation, but it does not state whether deletion is permanent, whether there are safety guards, what permissions are required, or what happens when the exclude parameter is supplied. The vague 'optional exclusion' adds little behavioral clarity.

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 a single front-loaded sentence with no filler. Every word contributes to the core meaning, and the destructive action is stated first.

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 destructive tool with no annotations and no output schema, the description is incomplete. It omits irreversibility, permission requirements, return values, and the precise interaction between pattern and exclude. An agent would need to guess at important behavioral details before invoking this tool.

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 0%, so the description must compensate. It does explain that 'pattern' is a glob pattern and hints that 'exclude' is optional, but it does not clarify the exclusion semantics, precedence, or whether both parameters use the same glob format. It adds some meaning but leaves important details unresolved.

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 the action ('Remove keys from storage'), the resource (storage), and the selection mechanism (glob pattern with optional exclusion). This distinguishes it from sibling tools like read_storage, write_storage, and cleanup_task_history without needing to inspect the schema.

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 gives clear context: use this tool when you want to delete storage keys matching a pattern. It does not explicitly mention alternatives or when-not-to-use scenarios, but the resource and action are self-evident enough to guide selection among the listed siblings.

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