Create Tag

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

Annotations already indicate this is a mutating operation (readOnlyHint=false) but not destructive. The description adds that a new tag is persisted and that the response includes the tag with its ID. It does not mention duplicate-name behavior or permissions, but for a simple create operation, the description provides adequate 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 one clear sentence that states the action and the return value with no filler. The essential behavior is front-loaded and every word contributes.

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 annotations already covering the mutation profile, the description is largely complete: it specifies the resource, the input, and the output. It could add a note about duplicate tag names or error conditions, but these are minor gaps for this simple tool.

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 description coverage is 100%, with the single 'name' parameter already documented as 'Tag name to create'. The description repeats this same meaning without adding extra format, uniqueness, or validation details. Baseline 3 is appropriate here.

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 uses a specific verb ('Create') with a clear resource ('a new tag in the ManyChat account') and states the result includes the created tag's ID. This clearly distinguishes it from sibling tools like list_tags (retrieval) and tag_subscriber (association).

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 verb 'Create' implies usage when a new tag is needed, but there is no explicit guidance about when to prefer this tool over alternatives, such as manychat_list_tags for existing tags or manychat_create_custom_field for fields. Usage context is implied rather than stated.

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