Delete custom field

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

The description repeats 'Destructive,' which is already captured by the destructiveHint annotation. It adds no additional behavioral context beyond the annotation, such as irreversibility, cascading deletion of field values, or permission requirements.

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 extremely brief ('Delete a custom field. Destructive.'), which is concise and front-loaded. However, it is perhaps too terse, missing opportunities to convey useful context without adding much length.

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, the description is incomplete. It does not mention that deletion is permanent or that it may affect associated data across entities. The destructiveHint annotation provides some safety awareness, but the description should elaborate on the consequences.

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 description coverage is 0%, and the description provides no information about the parameters (id and entity_type). It does not explain how to specify which custom field to delete or what the enum values mean, leaving the agent with only raw schema names.

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 tool's function: 'Delete a custom field.' It uses a specific verb (delete) and resource (custom field), and this distinguishes it from sibling tools like create, update, list, or get for 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 is provided about when to use this tool versus alternatives, such as choosing between custom fields and catalog custom fields, or any prerequisites. The description only states the action and a warning, with no context for decision-making.

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