delete_a_custom_deal_field_meta

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

Annotations already set destructiveHint=true and readOnlyHint=false. The description adds '🔴 DESTRUCTIVE · deletes data' and 'Confirm with the user before calling,' which reinforces the destructive nature and imposes a procedural requirement beyond the annotation hints.

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 concise, front-loaded with the destructive warning, and includes actionable instruction. It could omit the HTTP method path as it adds little value for agent invocation, but overall it is efficient and scannable.

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 the tool's simplicity (single parameter, no output schema, annotations present), the description provides sufficient context: purpose, destructive nature, and user confirmation requirement. No critical gaps are apparent.

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% and the parameter 'id' is described as 'ID of the field to delete' in the input schema. The tool description adds no additional meaning beyond this, so baseline score of 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 'Delete a custom field' and 'Deletes a record,' indicating the verb (delete) and resource (custom field meta). While it does not explicitly distinguish from sibling delete tools, the name 'delete_a_custom_deal_field_meta' is specific enough to avoid ambiguity.

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 instructs 'Confirm with the user before calling,' providing clear guidance on when and how to use the tool. It does not explicitly mention alternatives or when not to use, but the destructive warning and confirmation requirement are strong contextual cues.

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