create_tag

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

Annotations declare destructiveHint=true, which for a creation tool is a notable behavioral claim the description never addresses — it says nothing about duplicate-name behavior, overwriting, permissions, or reversibility. The description adds only the location scoping, so it neither explains nor contradicts the destructive hint, leaving the agent with an unresolved ambiguity.

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?

A single front-loaded sentence with no filler; nothing redundant. It is not padded, though it is also too spare to earn a 5 on structure alone.

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 one-parameter create tool with no output schema, the essentials are covered and the parameter is documented. However, given the destructiveHint annotation, the definition is incomplete about what the destructive behavior actually is and whether re-creating a name collides.

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?

Only one parameter exists and the schema describes it fully at 100% coverage ('Name for the new tag'), so the schema does the heavy lifting. The description adds no format, length, or uniqueness semantics beyond what the schema already states.

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?

States a specific verb+resource ('Create a new tag') and adds scope ('in the current GoHighLevel location'), so the action is unambiguous. It does not differentiate itself from any sibling (e.g., list_tags for checking existing tags) or clarify whether tag creation is idempotent, so it stops short of a 5.

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?

There is no when-to-use, when-not-to-use, or alternative guidance. The only hint of context is the 'current location' scoping, which an agent must infer places the tag in the active sub-account rather than anywhere else.

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