Create tag

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

Annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation. The description adds only the endpoint 'POST /v2/tags', which is a technical detail but not behavioral context such as duplicate handling, return values, or side effects. Given the openWorldHint is true, more disclosure would be valuable.

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 short but repeats itself: 'Create tag' and 'Creates a new tag' are redundant. The endpoint line adds useful technical info. It is not overly verbose, but not every sentence earns its place due to the duplication.

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 one-parameter creation tool, the description is minimally viable. It lacks any mention of return values, error conditions, or side effects, but the absence of an output schema and the low complexity keep it adequate. More context about duplicate tags or permissions would improve completeness.

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?

The input schema covers 100% of the single parameter 'name' with the description 'The tag name.' The tool description does not add any additional parameter semantics beyond the schema. Since schema coverage is complete, the baseline of 3 applies.

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 the action and resource: 'Create tag. Creates a new tag.' The verb 'create' and resource 'tag' accurately distinguish this from sibling tools like updateTag or deleteTag. However, it is somewhat redundant and lacks additional scope differentiation (e.g., what kind of tag), so it does not earn 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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, when to prefer createTag over other tag-related operations like tagDevices or updateTag, or any exclusions. The description only states the basic action.

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