ghl_custom_field_delete_folder

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

Annotations already mark the tool as destructive and idempotent. The description adds OAuth scopes and the object support limitation. However, it fails to disclose what happens when a folder is deleted (e.g., impact on custom fields inside it). The contradictory 'Create' text also harms transparency.

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 poorly structured. A div with incorrect 'Create' text appears, and the info callout is not clearly separated. The endpoint and scopes are technical details that could be omitted or presented more concisely.

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 straightforward delete operation with two parameters, the description lacks key context about the folder resource, how to find the id, and expected response. The info callout adds some value but overall the description is incomplete.

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 50% (only locationId has a description). The description does not explain the 'id' parameter (folder ID) or how to obtain it. No examples or additional context are provided to clarify parameter usage beyond the schema.

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 title and tool name indicate 'delete', but the description includes a div with 'Create Custom Field Folder' which directly contradicts the purpose. This inconsistency severely undermines clarity. The tool deletes a custom field folder, but the misleading text confuses the agent.

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 provides a constraint (only supports Custom Objects and Company) and endpoint details, but no explicit guidance on when to use this tool versus related tools like ghl_custom_field_create_folder or ghl_custom_field_update_folder. The agent is left to infer usage from the name alone.

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