create_tag

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

The description only covers the conceptual nature of tags, not behavioral traits like duplicate handling, slug generation defaults, or any side effects. Annotations only include openWorldHint=false, which does not disclose mutation or safety behavior, so the description carries the burden but fails to provide this context.

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 compact with two sentences, front-loading the core action and using an illustrative contrast. Every word earns its place without redundancy.

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 simple creation tool with one required parameter, the description adequately explains the purpose and distinguishes tags from categories. Gaps exist around behavioral details like uniqueness or slug defaults, but these are partially mitigated by schema fields and the straightforward nature of the 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%, so the schema already fully documents each parameter. The description adds context about tag semantics but does not provide additional per-parameter meaning 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 uses a specific verb 'Create' with a clear resource 'product tag', and contrasts tags with categories to clarify they are flat labels without hierarchy. This distinguishes the tool from sibling tools like create_category and update_tag.

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 explicitly illustrates usage with examples ('Bestseller', 'New Arrival') and contrasts with categories ('unlike categories, they have no hierarchy'), providing context on when to use tags instead of categories. However, it doesn't explicitly state exclusions or formal alternatives.

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