Delete GoHighLevel Custom Field

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

Annotations already mark destructiveHint: true, so the description reinforces this. It adds behavioral context by detailing the prerequisite of confirm and owner approval. No contradiction with annotations (readOnlyHint: false, destructiveHint: true align).

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?

Single sentence that front-loads the action and endpoint. No unnecessary words, but could be slightly expanded for readability. Efficient.

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 4 parameters, annotations, and no output schema, the description covers the key aspects: action, resource, confirmation requirement, and owner approval. It would benefit from noting irreversibility, but destructiveHint covers that. Adequate.

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 all parameters. The description adds minimal extra semantics (the endpoint path implies locationId position but the schema already describes it). Baseline 3 is appropriate.

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 the action (Delete) and the resource (custom field) with the specific endpoint path. It distinguishes this destructive action from create, update, get, and list tools among siblings.

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 explicitly requires confirm: true and owner approval before execution, guiding the agent to only invoke when certain and with confirmation. However, it does not differentiate between the v1 and v2 delete tool (both exist as siblings).

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