cm_delete_custom_field

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

The description includes a warning emoji (⚠️) and the annotation sets destructiveHint=true, indicating it is a destructive operation. However, it does not add further context about consequences such as irreversible deletion or effect on related data.

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?

A single sentence with a warning symbol, front-loaded and precise. Every word is necessary, no redundancy.

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 simple delete operation with two required parameters, the description is largely adequate. However, it could mention that deletion is permanent or require specific permissions, but given the destructiveHint annotation, it is sufficient.

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% with clear descriptions. The description does not repeat parameter info but does provide a helpful example for customFieldKey (e.g., '[MyField]'). This adds value beyond the schema.

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 verb 'Delete' and the resource 'custom field from a list'. It is specific and distinguishes this from sibling tools like cm_update_custom_field and cm_get_custom_fields.

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 on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or suggest when to use other tools. The agent must infer usage from the name and description alone.

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