st.worldbook.delete

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

With no annotations, the description carries the behavioral disclosure burden and does reveal that deletion is gated by confirm and requires prior snapshots. However, it does not state whether deletion is irreversible, what 'snapshots first' means concretely, or what side effects occur beyond removal of the file.

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 sentences, front-loaded with the action, and no filler. The precondition is compressed into a short second sentence, and every word contributes.

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, this is too sparse: it lacks a concrete workflow, irreversibility information, and any mention of return or error behavior. An agent can infer the basics but cannot reliably perform a safe deletion without more context.

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, but it only maps confirm to true and vaguely gestures at snapshots. The required name and optional snapshotLabel are never explained, leaving agents to guess how to fill them.

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?

States the exact operation ('Delete a worldbook file') with a specific verb and resource. It clearly applies to whole-file deletion rather than entry-level operations, distinguishing it from siblings like st.worldbook.entry.configure, though it does not explicitly name an alternative.

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?

Provides direct preconditions: confirm must be true and snapshots must exist first. This gives an agent actionable constraints, though it does not explain when to avoid deletion or how to coordinate with st.snapshot/st.rollback.

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