whim_context_delete

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

No annotations are provided, so the description carries the full disclosure burden. For a destructive operation, there is zero behavioral disclosure: no mention that the operation permanently removes data, no mention of idempotency, no note about what happens to the slot's contents or any cascading effects. The description is merely a label that adds no transparency beyond the name, and absent annotations, this is a significant gap for a destructive call.

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?

Three words and a period, with the verb front-loaded. Zero filler, zero redundancy. For a simple CRUD delete where the schema covers all parameters, extreme leanness is appropriate and not under-specification. It fully adheres to 'every sentence earns its place' by having exactly one minimal sentence.

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 low-complexity tool (2 params, no enums, no nested objects, no output schema) with 100% schema coverage, the description is arguably just enough: the schema documents both parameters, the siblings define the CRUD family, and the verb defines the action. Minor deduction: a warning about the destructive nature of the operation or its namespace scoping would push this to a 5, but completeness is relative to a deliberately simple 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?

The schema already covers 100% of parameters with precise descriptions (key = "Context slot name", namespace with default "default"), so the baseline is 3. The description "Delete a context slot" adds no additional parameter semantics — it doesn't clarify how key and namespace interact, nor the semantics of passing no namespace (e.g., is a key deleted globally or within the default namespace?). No value-add beyond schema, but no harm either.

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 precise verb ("Delete") and resource ("context slot"), and is clearly distinct from siblings like whim_context_get/set/list. The verb disambiguates it within the CRUD family and the tool name reinforces the same contract. Slight deduction: "context slot" is opaque without further explanation, and it's unclear whether the deletion is scoped per-namespace or if the action is cryptographically irreversible.

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 intended use case is implied by the sibling CRUD pattern (get/set/list/delete for context), so an agent can infer when this applies. However, there is zero explicit guidance about edge cases or exclusions — what happens if the supplied key doesn't exist? Is deletion permanent and irreversible? No mention of whether the namespace parameter is required to target the correct slot. The description leaves the agent to assume from the verb alone.

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