delete_a_field

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

The description reinforces the destructive nature with '🔴 DESTRUCTIVE · deletes data' and 'Deletes a record,' adding clarity beyond the annotations (destructiveHint=true). It also instructs user confirmation. No contradiction with annotations.

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 with a header line (emoji, HTTP method) and a brief statement. Some redundancy exists between 'Delete a custom field' and 'Deletes a record,' but overall it is efficient.

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-by-ID tool, the description provides the necessary warnings (destructive, confirm with user) and identifies the resource. It is adequate given no output schema and a single required parameter.

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 covers the parameter 'id' with 100% coverage, describing it as 'ID of the field option to delete.' The description does not add additional meaning about the parameter, so baseline 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 includes 'Fields' in the header, making the resource clear. However, it also says 'Deletes a record,' which could be slightly misleading, and there is a sibling tool 'delete_a_custom_field' that may overlap.

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 says 'Confirm with the user before calling,' which provides a usage guideline. However, it does not specify when to use this tool versus alternatives (e.g., delete_a_custom_field) or when not to use it.

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