Create Tag

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds minimal behavioral context. It clarifies that the tag can be created from various refs (branch, commit, tag), but does not discuss side effects, permissions, or other behaviors beyond what annotations already convey.

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 very concise (one sentence), but it lacks structure. Breaking it into a brief overview and parameter details would improve readability without adding significant length.

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 4 parameters, no output schema, and a creation operation, the description is inadequate. It does not explain what is returned (e.g., the created tag object), error conditions, or that project_id is optional (defaulting to the current project). The agent lacks sufficient context to use this 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?

With 0% schema description coverage, the description should compensate by explaining parameters. However, only the 'ref' parameter is implicitly explained via 'from a branch, commit SHA, or another tag'. The 'tag_name', 'message', and 'project_id' parameters are not elaborated in the description, leaving the agent without key semantics.

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 tool's purpose: creating a repository tag from a branch, commit SHA, or another tag. It uses a specific verb (Create) and resource (repository tag), distinguishing it well from sibling tools like gitlab_delete_tag, gitlab_get_tag, and gitlab_list_tags.

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 provides no guidance on when to use this tool versus alternatives (e.g., gitlab_create_branch, gitlab_create_release). There is no mention of prerequisites, typical use cases, or when not to use it.

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