Delete project CI/CD variable

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

The description adds a behavioral detail beyond the annotations: 'without returning its former value.' This is useful context that annotations do not cover Flagged as (readOnlyHint=false, destructiveHint=true) already, but the description adds the specific behavior of not returning the deleted value, which is valuable for the agent.

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 concise at one sentence, stating the core action and a key behavioral detail. It is front-loaded with the verb and resource. However, it is extremely terse, almost to the point of being minimal, but it does not waste words.

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?

The description is incomplete for a tool with three parameters, especially because schema coverage is only 33%. The optional 'filter_environment_scope' parameter is not explained, and the description does not mention any prerequisites or side effects beyond what annotations already provide. It lacks enough context for the agent to fully understand the tool's behavior.

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 only 33%, with only the 'project' parameter described. The description does not clarify `key` or `filter_environment_scope` semantics, leaving ambiguity. Since the description adds no parameter context beyond the schema's minimal coverage, it fails to compensate for the low 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 the tool deletes a project CI/CD variable, using a specific verb and resource. It distinguishes itself from sibling tools like create/update/list variables by explicitly saying 'Delete'. The added detail about not returning the former value further clarifies its behavior.

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 guidance is provided on when to use this tool versus alternatives (e.g., delete_group_ci_variable, or get/update tools). The context of usage is entirely implicit from the name. There is no mention of preconditions or when this tool is appropriate compared to others.

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