Create project CI/CD variable

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

Annotations already communicate readOnly=false, destructive=false, and idempotent=false. The description adds one genuinely useful behavioral detail—that the variable's value is not returned—but does not disclose replacement behavior, auth requirements, or what happens on duplicate keys. This is modest added value 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, front-loaded sentence with no filler. Every word contributes meaning, including the non-obvious detail that the created variable's value is not returned.

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?

For a 10-parameter mutating tool with sparse parameter documentation, this one-sentence description is too thin. It does not address duplicate variable behavior, environment scoping, variable type implications, or project vs group selection guidance. The presence of an output schema reduces the need to explain return values, but does not compensate for these gaps.

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 only 30% schema description coverage and 10 parameters, the description should compensate by explaining or contextualizing parameters like masked, protected, variable_type, and environment_scope. It does not; it only restates the tool's action. The sparse schema descriptions and parameter names are left to carry the burden.

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 uses a specific verb ('Create') and resource ('project CI/CD variable'), and adds a useful behavioral differentiator: 'without returning its value.' This clearly distinguishes it from sibling tools like create_group_ci_variable, update_project_ci_variable, and list_project_ci_variables.

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 makes clear this is for creating project-level CI/CD variables, as opposed to group-level or update/list operations implied by sibling names. However, it does not explicitly state when-not-to-use it, such as whether to call update_project_ci_variable instead if the variable already exists.

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