ghl_custom_field_create_folder

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

Annotations indicate a write operation (readOnlyHint false). The description adds OAuth scopes and endpoint URL, but lacks details on side effects, idempotency, or error conditions. For a creation tool, more behavioral context (e.g., what happens if folder exists) would be valuable.

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 and front-loaded with the core purpose. However, it includes redundant HTML formatting and a repeat of the title, which could be streamlined. Overall, it is efficient but has minor noise.

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?

No output schema exists, and the description does not describe the return value (e.g., folder ID, success indicator). For a creation tool, this is a significant gap. Additionally, it does not explain what a custom field folder is or how it relates to custom fields, leaving the agent without full context.

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 clear descriptions for each parameter. The description adds context by noting which objects are supported, which directly clarifies the 'objectKey' parameter's allowed values. This extra guidance goes beyond what the schema alone provides.

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 it creates a custom field folder and specifies supported objects (Custom Objects, Company). The tool name and description differentiate it from sibling tools like ghl_custom_field_create, which creates individual fields, not folders.

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 usage for supported objects but provides no explicit guidance on when to use this tool versus alternatives (e.g., ghl_custom_field_update_folder, ghl_custom_field_delete_folder). The info note about supported objects is helpful but incomplete for context-aware selection.

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