wb_tag_create

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states that a tag is created and that color is HEX, with no mention of return values, duplicate handling, side effects, or required permissions. This is minimal transparency for a tool that performs a state-changing operation.

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 a single front-loaded sentence with no wasted words. It states the action first and then adds the relevant color constraint. The parenthetical Russian phrase is mildly redundant but not harmful.

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?

Given the simple schema and lack of output schema, the description gives the essential action and one parameter detail, but it omits important context such as success/failure behavior, whether duplicate tags are allowed, and how the new tag relates to tag-linking or card operations. With no annotations to fill these gaps, the description feels incomplete.

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 0%, so the description must compensate for both parameters. It adds value for the color parameter by specifying HEX format, but it offers no semantic guidance for the required name parameter. The description does not fully cover the parameter space.

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 a tag.' It also identifies a key attribute (color is HEX), making it distinguishable from sibling tools like wb_tag_update, wb_tag_delete, and wb_tag_link. The broader purpose of a tag is not explained, but the core meaning is clear.

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 explicit guidance on when to use this tool versus alternatives. The create/update/delete distinction is inferable from sibling names, but no prerequisites, exclusions, or context for tag creation are provided. The description does not help an agent decide between wb_tag_create and wb_tag_link or wb_tag_update.

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