Delete pipeline schedule variable

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine value beyond that: it confirms successful deletion returns no data, names the three required identifiers, and enumerates the two exception types raised on missing/invalid parameters. It does not mention permission requirements or confirm irreversibility, which keeps it from a 5.

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 one-line purpose is front-loaded and effective, but the rest is a docstring template whose central payload ('e.g., project_id, pipeline_schedule_id, key') is buried inside a generic **kwargs bullet. The Returns and Raises sections earn their place; the 'Args: **kwargs' framing is boilerplate that obscures the required-parameter signal.

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?

With no output schema, explaining that deletion returns no data is valuable and present, as is the error surface. But for a destructive operation against a 126-parameter schema with no required fields, the description should explain that most schema properties are irrelevant and clarify which identifiers are mandatory versus optional — that gap leaves real ambiguity about how to invoke the tool correctly.

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 coverage is 0% across a sprawling 126-parameter, zero-required catch-all schema, so the description carries a heavy burden. It partially compensates by naming the three parameters that actually matter (project_id, pipeline_schedule_id, key), which is the single most important signal given no required fields are marked. However, it says nothing about the other 123 parameters — whether they are irrelevant, passthrough, or aliases (e.g. 'id' vs 'project_id') — leaving the agent to guess.

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 variable from a pipeline schedule'), which is immediately distinguishable from the sibling create/create-schedule tools by name and intent. It stops short of explicitly naming the neighboring tools (e.g. gitlab_create_pipeline_schedule_variable, gitlab_delete_pipeline_schedule), so the differentiation is implicit through naming rather than stated.

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?

There is no when-to-use or when-not-to-use guidance and no alternative tools are named. The only indirect usage signal is the Raises section, which reveals that project_id, pipeline_schedule_id, and key are required — useful, but not the same as telling the agent when this tool is the right choice.

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