ghl_email_builder_template_create

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

Annotations already indicate it's a write operation (readOnlyHint false) and not idempotent. The description adds endpoint details and version but doesn't disclose side effects, error behavior, or concurrency implications.

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?

Short and focused, with key information front-loaded. One sentence for purpose, then technical details. No fluff but could be more structured with separate sections.

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?

Missing output schema, no explanation of the complex nested body parameters or their relationships. The description provides endpoint and scopes but not enough to fully understand usage beyond basic creation.

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% for the single parameter, but the description of the parameter is generic. It doesn't explain the meaning of enum values like 'type' (html, folder, etc.) or 'importProvider', which would help the agent choose correctly.

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?

Clearly states it creates a new email builder template, explicitly calling it 'Legacy' and distinguishing it from the v3 template family. The verb 'Create' and resource 'template' are specific.

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?

Explicitly says it's a legacy API distinct from v3 templates, guiding when to use this vs. alternatives. Also specifies required OAuth scopes, which helps with authorization context.

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