Delete tag

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

Annotations already declare destructive=true, idempotent=true and openWorld=true, so the safety profile is covered. The description adds value by noting the successful response contains no data and by listing MissingParameterError/ParameterError conditions, but it omits whether protected tags block deletion or what permissions are required.

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 docstring is front-loaded with purpose and reasonably short, but the Args/Returns/Raises boilerplate devotes space to kwargs while omitting real parameter detail, and the 'name' reference is wasted/misleading text.

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?

A destructive, 8-parameter tool with no output schema and zero schema description coverage gets an inadequate description: parameter names are wrong, pagination params are unexplained, and protected-tag/permission behavior is not addressed.

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% across 8 parameters, so the description must compensate and does not. Worse, it names 'project_id, name' while the schema's parameter is 'tag', which is actively misleading; pagination-style params (page, per_page, max_pages) on a delete operation are left unexplained.

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?

States a specific verb and resource ('Delete a tag in a project'), which is clearly distinguishable from siblings like gitlab_create_tag, gitlab_get_tag, and gitlab_delete_branch. It does not explicitly reference those siblings, but the purpose is unambiguous.

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 indication of when to use this versus alternatives (e.g., gitlab_unprotect_tag, or checking gitlab_get_protected_tag first). No preconditions such as required permissions or protected-tag status are stated.

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