Create a tag

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

Annotations indicate a mutating, non-idempotent, non-destructive operation. The description adds concrete behavioral details: slug conflicts return 409 SLUG_CONFLICT, changes are not public until a separate publish call, and a secret key with taxonomy:write scope is required. These go well beyond the annotations.

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?

Four concise sentences, each providing a distinct piece of information: action, uniqueness constraint, side effect, and auth requirement. The description is front-loaded with the primary action and contains no filler.

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 create tool with two parameters and no output schema, the description covers essential aspects: conflict behavior, publication independence, and credential requirements. It is sufficiently complete for an agent to select and invoke the tool correctly.

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 covers slug's derivation but name has no description. The description explains slug uniqueness and conflict behavior but omits details about the 'name' parameter. With 50% schema coverage, the description only partially compensates, leaving name semantics implicit.

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 a specific verb and resource: 'Create a tag.' It adds context that the tag is created on the customer's Site, which is unambiguous and distinguishes it from other create tools by resource.

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?

Provides useful context: slug uniqueness, publishing is separate, and auth requirements. It implies when to use the tool (for creating tags) and notes that publishing is a separate call, but it does not explicitly mention alternative tools or exclusions. This is clear context without direct exclusions.

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