fields_delete_deal_field

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

No annotations are provided, so the description carries full burden. It discloses that the delete is soft, values are preserved, and the field stops appearing in UI and new payloads. This is key behavioral information for a delete operation, though it does not cover authorization or error states.

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?

Three sentences: first states the action, second explains behavioral implications, third provides an alternative for bulk. No wasted words, front-loaded, and efficiently conveys all necessary 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 simple delete tool with one parameter and no output schema, the description covers the key points: action, soft-delete behavior, and alternative for bulk. It lacks details on return values or error scenarios, but is sufficient for most use cases.

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 the parameter description already stating 'ID of the deal field to delete.' The description adds minimal value beyond this, only clarifying that it is a custom deal field. Baseline 3 is appropriate as schema does the heavy lifting.

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 a custom deal field by ID.' It specifies that it is a soft-delete, preserving values but hiding the field. It also distinguishes from the sibling bulk delete tool by mentioning it is for a single field, providing clear purpose differentiation.

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 explicitly directs to use `fields_bulk_delete_deal_fields` for deleting multiple fields, offering a clear alternative for batch operations. It does not explicitly state 'when not to use' but implies single vs. bulk usage, providing adequate guidance.

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