delete_custom_field_field_group

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

Annotations already indicate it's a write operation (readOnlyHint false), not destructive (destructiveHint false), and idempotent. Description adds context that it unlinks records and is reversible, which is consistent. However, it could specify that it deletes a group member association, not the field group itself.

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?

Description is short and includes useful meta information (emoji, HTTP method). Every sentence adds value, though the structure could be cleaner (e.g., integrating the emoji line with the main description). No wasted words.

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 no output schema and simple parameters, the description explains the core effect (removing an association) and reversibility. However, it lacks specificity about which entities are unlinked (custom fields and field groups) and the example given (untagging contacts) seems mismatched with the tool name.

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 descriptions for both parameters (body, groupID). The description does not add any meaning beyond what the schema provides. For example, 'groupID' could be clarified as the ID of the group member association, not the field group ID.

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?

Description states it removes an association between records and is reversible. However, the tool name 'delete_custom_field_field_group' could be misinterpreted as deleting the field group itself, while the description clarifies it's an unlinking operation. This is somewhat clear but could be more explicit about what entities are unlinked.

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?

No explicit guidance on when to use this tool versus alternatives like 'delete_a_custom_field_group' or 'add_custom_field_to_field_group'. The description does not differentiate from sibling delete tools or provide context on when unlinking is appropriate.

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