Tag actions

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description merely restates the create/delete behavior without adding new context such as irreversibility, permissions, or side effects. It adds little beyond the annotations.

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 concise sentence, which is efficient, but it is under-specified for a tool with 5 parameters and two possible actions. It does not over-explain, but its brevity crosses into being vague, similar to the 'Process' example.

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 no output schema and partial parameter descriptions, the description should explain return values, error conditions, or the effect of the operation. It only states the core action, leaving out critical usage details like project_id fallback and ref requirements.

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 60% schema coverage, the description should compensate for undocumented parameters like action and tag_name, but it only echoes the schema's enum values ('creates or deletes') and does not clarify ref, message, or project_id semantics. It adds no meaningful parameter meaning beyond the schema.

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 creates or deletes a tag, which is a specific verb+resource pairing. However, it does not differentiate from sibling tools like gitlab_list_tags, and the scope (e.g., project context) is not mentioned, preventing a perfect score.

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, no mention of prerequisites (e.g., project_id fallback), and no exclusions. It is a bare statement of functionality without contextual usage directions.

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