delete_storage_config

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

The annotations already convey that the operation is destructive and not read-only, so the description adds no behavioral information beyond what is already structured. It does not disclose consequences such as whether deleting a storage configuration cascades to dependent resources or whether the operation is reversible in any way.

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 one sentence with no filler, and it front-loads the core action and resource. For a simple single-parameter delete operation, this level of conciseness is appropriate.

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?

The description is minimally viable when combined with the schema and annotations: the schema defines storage_id as required, and the annotations indicate destructiveness and idempotency. However, it leaves out any indication of side effects, return behavior, or how this delete differs from the many sibling delete/config/storage tools.

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?

With 0% schema description coverage, the description must compensate for the lack of parameter documentation, but it does not explicitly mention storage_id or explain how to determine its value. The phrase 'storage configuration' loosely maps to storage_id, but this is minimal semantic help beyond the schema's own property name.

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 uses a specific verb ('Delete') and a specific resource ('storage configuration'), making the tool's purpose immediately clear. It distinguishes itself from sibling tools like delete_config or delete_schedule by naming the storage-specific resource, though it does not explicitly differentiate itself from those siblings.

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 such as delete_config, delete_schedule, or update_storage_config. There is no stated context, prerequisite, or 'use instead' hint, leaving the agent to infer usage solely from the tool name.

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