ghl_email_template_folder_create

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

The description adds OAuth scopes and endpoint details beyond the annotations, which are minimal. However, it does not disclose behaviors like idempotency, error conditions, or what happens if the folder already exists. Annotations already indicate non-destructive and non-idempotent, so the additional context is useful but not extensive.

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 fairly concise with four lines, but the first two lines ('Create a template folder, Create a new template folder') are redundant. Endpoint and OAuth scopes are useful but could be more streamlined.

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 is present, and the description does not explain what the response contains. It lacks information on error handling, prerequisites, or examples. For a creation tool, more context is needed to understand the expected result.

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 input schema has 100% coverage with descriptions for both parameters. The tool description adds no further explanation of parameters, but given full schema coverage, this is acceptable. No additional value is provided 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 description clearly states 'Create a template folder' and repeats 'Create a new template folder', making the action unambiguous. The tool name and description align, and it is distinct from siblings like ghl_email_template_create which creates templates themselves.

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 guidance is provided on when to use this tool versus alternatives, such as other folder creation tools (e.g., custom_field_create_folder, media_create_folder). The description lacks context for tool selection.

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