delete_dataset

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

The description discloses that the operation is irreversible and requires re-indexing to use again, going well beyond the readOnlyHint=false annotation. It also specifies that the SQLite store is removed, providing concrete destruction details.

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 three short sentences, each serving a distinct purpose: action, benefit, and consequence. No redundant words.

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 delete tool with one parameter and no output schema, the description covers the core behavior, disk-space motivation, and irreversibility. It does not specify the return value or error handling, but that is arguably unnecessary for this level of complexity.

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 single parameter 'dataset' is fully described in the schema with 'Dataset identifier to delete (from list_datasets),' and the tool description adds no additional parameter information. Since schema coverage is 100%, the baseline of 3 applies.

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 'Delete an indexed dataset and its SQLite store,' identifying the specific verb and resource. This distinguishes it from siblings like list_datasets or describe_dataset, which are non-destructive.

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 includes 'Frees disk space,' indicating the practical reason to use this tool. It does not explicitly reference alternatives or exclusions, but the context is clear enough for a delete operation.

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