delete_merge_field

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

The description adds significant behavioral context beyond the annotations. It explicitly states that all stored data is permanently lost, aligning with destructiveHint:true. It also discloses that default fields will return an error, which is not in annotations. No contradiction with annotations.

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 concise and well-structured: it starts with the purpose, gives usage guidance, explains parameters, describes return value, and provides an example. Every sentence adds value, and it is front-loaded with the most important information.

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 delete operation, the description is complete. It covers the action, input parameters, constraints, return value format, and an example. Given the output schema is described in text and the sibling tools list, no additional context is needed.

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?

Although the schema has 0% description coverage, the description provides clear semantics for both required parameters: list_id (with example and source) and merge_id (with type, source, and constraint). The 'account' parameter is not explained, but it is optional and likely not needed, so the description compensates well for the key params.

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 a custom merge field and all its stored data from an audience.' This is a specific verb+resource combination that distinguishes it from sibling tools like update_merge_field or create_merge_field. It also specifies that default fields cannot be deleted.

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 explicit usage guidance: 'Use only when you no longer need the field.' It warns that default fields cannot be deleted and will return an error, and it advises using list_merge_fields to find merge_id values. This clearly tells when and when not to use the tool.

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