Delete a Marketing Cloud Next / Data 360 record

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

With no annotations, the description carries the full behavioral burden and does disclose the most critical traits: the operation is destructive and gated by an environment variable. It stops short of stating irreversibility or success/error behavior, but the destructive guardrail is substantive.

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 definition is a single compact sentence that front-loads the action and follows with necessary constraints. The parenthetical 'kind "delete"' is slightly redundant with 'Delete', but the overall structure has no fluff.

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?

The description covers the safety gate and path requirement, and the schema documents all parameters. However, with no output schema it does not describe what a successful delete returns or whether deletion is permanent/irreversible, leaving an agent without a complete model of the call's result.

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 baseline is 3. The description adds value by warning that the path parameter is required even though pathParams is not marked required in the schema, and it does not repeat the schema's property descriptions.

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 states a specific verb and resource ('Delete a record') and reinforces it with the HTTP method DELETE. The name and title additionally scope it to Marketing Cloud Next / Data 360, clearly distinguishing it from the SF delete siblings and from mcnext_create/update/action.

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?

It provides actionable invocation context: the path parameter is required, and the tool is blocked unless MC_NEXT_ALLOW_DESTRUCTIVE=true. This tells the agent the preconditions and an explicit condition under which not to attempt the call, though it does not name alternative tools.

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