gitee_create_tag

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

With no annotations, the description carries full burden for behavioral traits. It only states 'Create a tag' without disclosing that the operation is destructive, requires specific permissions (e.g., write access), or that tag_message creates an annotated tag. Side effects like overwriting an existing tag are not mentioned.

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 extremely concise at 3 words, which is efficient for a simple tool. However, it could benefit from a brief sentence to add context without losing brevity. It is front-loaded but may sacrifice completeness.

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 lack of annotations and output schema, the description should explain what happens after creation (e.g., tag is visible in tag list, releases can reference it) and disclaimers about branching. The optional tag_message and body parameters are not mentioned, and the relationship with gitee_create_release is unclear.

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 has 100% coverage with clear parameter descriptions. The description adds minimal value beyond the schema, but the schema itself already provides sufficient semantic meaning for each parameter. Baseline 3 is justified, and the tool's simplicity earns a slight bonus for clarity.

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 'Create a tag' clearly states the verb and resource, but it does not differentiate from sibling tools like gitee_create_release, which also relates to tags. It is specific enough to convey intent, but lacks distinguishing context.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, allowed parameter combinations, or exclusions such as whether to use gitee_list_tags for listing or gitee_create_release for release creation.

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