delete_datahub_dataset

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

The description is misleading by starting with 'Ingest...' which conflicts with the delete action. Annotations correctly mark destructiveHint: true, but the description adds confusion instead of clarity. No mention of consequences (e.g., irreversible deletion) beyond what annotations already indicate.

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, but the first sentence is irrelevant and misleading. The structure is not concise because it includes unnecessary information (ingestion) that harms clarity.

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?

Given the tool is destructive, has no output schema, and one parameter lacks description, the description is critically incomplete. It fails to mention that deletion is permanent, error conditions, or any required preconditions.

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 50% (only customerContext has a description). The tool description does not explain the 'name' parameter at all, leaving ambiguity about what name refers to (dataset ID? name string?). The description adds no value beyond the schema.

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 starts with 'Ingest third-party cost...' which suggests a create/ingest action, then contradicts with 'Deletes a specific DataHub dataset.' The purpose is vague and inconsistent, and it does not distinguish from sibling tools like 'delete_datahub_datasets' (plural).

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 vs alternatives. No prerequisites (e.g., dataset must exist) or context for deletion. Sibling tools include delete_datahub_datasets, but no differentiation is provided.

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