Delete custom value

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

The description says 'Destructive,' which merely repeats the destructiveHint annotation. It adds no additional behavioral context such as whether deletion is permanent, affects related entities, or requires special permissions. With annotations already carrying the safety profile, the description adds nothing beyond what structured data provides.

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 only two sentences, but both are redundant: 'Delete a custom value' restates the title, and 'Destructive' restates the annotation. It achieves brevity at the cost of essential information, making it under-specified rather than genuinely concise.

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 destructive operation with no output schema, the description should explain consequences (e.g., irreversibility, cascading effects) and what a custom value is. It provides none of this, leaving the agent without enough context to confidently invoke the tool or interpret results. The sibling list contains many similarly named delete tools, increasing the need for differentiation.

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 schema describes locationId but leaves customValueId without a description (50% coverage). The description does not explain the purpose or format of either parameter, nor does it compensate for the missing customValueId documentation. For a required parameter, this is a significant gap.

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 and resource: 'Delete a custom value.' This is specific and not a pure tautology, though it closely mirrors the title. It doesn't explicitly differentiate from sibling delete operations like ghl_delete_custom_field, but the resource name is distinct enough for an agent to identify the operation.

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 is provided on when to use this tool versus alternatives such as ghl_update_custom_value or ghl_delete_custom_field. There is no mention of prerequisites, use cases, or exclusions. The agent must infer usage from the tool name alone.

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