Remove a DataSource definition while preserving collected data. Requires write permission to delete.
Delete a DataSource definition (requires write permission). Existing collected data is retained.
| Name | Required | Description | Default |
|---|---|---|---|
| datasource_id | Yes | DataSource ID to delete |
Changes observed during successful MCP inspections.
v4.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds meaningful behavioral context beyond the annotations: the permission requirement and the fact that existing collected data is retained. This complements the destructiveHint and idempotentHint annotations without contradicting them.
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 no filler. The core action is front-loaded, and the permission and data-retention details each earn their 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 single-parameter destructive action, the description covers the essential call-time knowledge: what is deleted, what is retained, and what permission is required. Annotations cover the destructive and idempotent behavior, so nothing critical is missing.
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 input schema already has 100% coverage with a clear description for datasource_id, so the description adds no new parameter-level meaning. A baseline score of 3 is appropriate because the schema carries the parameter documentation burden.
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 a specific verb ('Delete') and resource ('DataSource definition'), making the scope clear: the definition, not the collected data. This distinguishes it well from sibling tools like create_datasource, update_datasource, and export_datasource.
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?
Gives a useful prerequisite ('requires write permission') and implies that data is safe to keep, but does not explicitly say when to choose this tool over alternatives or when not to delete. The usage context is clear but no exclusions or alternative routing are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.