remove_deal_field

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

No annotations are provided, so the description fully carries the burden. Clearly indicates destructive behavior with 'PERMANENTLY lost' and explains backup limitations. Details refusal conditions, providing comprehensive behavioral context.

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, well-structured, and front-loaded with the critical warning. Every sentence provides essential information without fluff.

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?

Despite a single parameter and no output schema, the description covers purpose, usage guidelines, behavioral details, and an alternative tool. It fully addresses the tool's complexity.

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 only parameter is 'field_id' (integer). The schema provides title and type, but the description does not add any additional meaning (e.g., how to obtain or identify field IDs). With 0% schema description coverage, the description could have compensated but did not. However, the parameter is self-explanatory.

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 deal field' with a specific verb and resource, and distinguishes from sibling 'clear_deal_custom_field' for per-deal cleanups. The purpose is unambiguous.

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?

Explicitly states when to use (delete a custom field) and warns about permanent data loss. Provides alternative tool 'clear_deal_custom_field' for per-deal cleanups. Lists conditions under which deletion is refused (protected keys, system fields).

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