delete_dataset

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

Without annotations, the description carries the full burden. It discloses the permanent nature of the deletion and clarifies that entities are not deleted, only associations. This adds important behavioral context beyond the obvious. It could mention permission requirements but overall is strong.

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 with zero waste. The first sentence front-loads the primary action, and the second adds crucial nuance. Every word earns its place.

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, the description covers the key behavioral detail (what happens to entities) and works well with the schema. An output schema exists to explain return values. Could hint at idempotency or error conditions, but not necessary for clarity.

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%, so the schema already documents both parameters. The description adds no extra meaning beyond restating the dataset_id parameter's purpose. Baseline of 3 is appropriate since the schema does the heavy lifting.

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?

Description clearly states the tool permanently deletes a dataset and explicitly clarifies that entities referenced by the dataset are not deleted. The verb 'delete' and resource 'dataset' are specific, and the description distinguishes it from sibling tools like delete_job or delete_entity.

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 implies use when you need to permanently remove a dataset, but it lacks explicit guidance on when to use this tool versus alternatives, when not to use it, or any prerequisites. No sibling comparisons or exclusions are mentioned.

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