Create group CI/CD variable

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

Annotations already indicate a write operation (readOnlyHint=false), so the description correctly adds the specific behavior of not returning the value, which is security-relevant. However, it does not disclose other potential behaviors such as idempotency (already false), permissions required, or side effects. With annotations covering the basic safety profile, the added detail earns a middle score.

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 that communicates the core purpose and a key behavioral trait. It is front-loaded, contains no redundancy, and every word adds value.

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 tool's complexity (10 parameters, 3 required, 30% schema coverage) and the existence of an output schema, the description is far too minimal. It does not provide context on when to use group vs project variables, prerequisites, or implications of setting flags like 'masked' or 'protected'. The single line does not sufficiently guide an agent for safe and correct usage.

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 schema has descriptions for only 3 of 10 parameters (30% coverage), placing a heavy burden on the description to clarify parameter semantics. The description adds zero parameter documentation, leaving many parameters (masked, protected, environment_scope, variable_type, etc.) unexplained. This fails to compensate for the low schema coverage.

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 that it creates a group-level CI/CD variable, with a specific verb ('Create') and resource ('group CI/CD variable'). It also adds a behavioral note about not returning the value, which distinguishes it from potential siblings that might return the value. This is specific and avoids confusion with update/delete/list tools.

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 like project-level variables or updates. It mentions no explicit 'when to use' or 'when not to use' conditions, nor does it reference sibling tools. The only hint is the group scope, which is implicit in the name. This is a clear gap for a tool with multiple related operations.

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