quire.deleteStorageValue

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

The annotation already marks the tool as destructive via destructiveHint=true. The description adds 'This action cannot be undone,' reinforcing the irreversibility. However, no other behavioral traits (e.g., permissions, side effects on related data) are disclosed, so it does not significantly exceed annotation coverage.

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?

Two concise sentences: the first states the core action, the second adds critical irreversibility information. No redundant words, and the purpose is front-loaded.

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 simple deletion operation with one parameter, the description covers the action and its irreversibility. Lack of output schema and no mention of return behavior are acceptable given the tool's simplicity. Slightly incomplete due to missing usage guidance, but adequate.

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 coverage is 100% with a description for the 'name' parameter. The description does not add any additional context or constraints beyond what is in the schema, so it meets the baseline.

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: 'Delete a stored value by name.' It uses a specific verb and resource, distinguishing it from sibling tools that delete other entities or perform other operations like get/put/list.

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 on when to use this tool versus alternatives like putStorageValue or listStorageEntries. The description does not specify prerequisites or preferred contexts, such as 'use only if value exists'.

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