Delete custom field value

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

Annotations already indicate destructive and idempotent behavior. The description adds the scope (organization, group, or device) and the API endpoint, but does not disclose potential side effects like cascading deletions when 'force' is used. It adds some context beyond annotations but remains minimal.

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 short but the first sentence 'Delete custom field value' is redundant with the title. The remaining two sentences provide useful scope and endpoint information, but the redundancy slightly reduces conciseness.

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?

The description gives the scope and endpoint, but does not explain behavior such as what happens with descendants or the effect of 'force'. Since the schema covers parameters, this is acceptable for a delete operation, but it could be more complete.

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 description does not explain any parameters beyond mentioning 'organization, group, or device', which overlaps with the assigned_to_id schema description. The schema already covers the parameters well, so the description adds little semantic value.

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 that the tool deletes a custom field value for an organization, group, or device. The verb 'deletes' and the resource 'custom field value' are specific, and the scope distinguishes it from other tools like deleteCustomField (which deletes the field itself).

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 implies the tool is used to delete a specific custom field value at various scopes, but it does not explicitly mention when to use it versus alternatives such as updateCustomFieldValue or deleteCustomField. There is no guidance on when to use the 'force' parameter or exclude certain cases.

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