delete_pipeline_variable

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a pipeline variable and returns a confirmation, which covers the basic action and output. However, it lacks critical details such as whether this operation is destructive/permanent, what permissions are required, if there are rate limits, or how errors are handled. For a deletion tool with zero annotation coverage, this is insufficient.

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 well-structured and concise, using a brief purpose statement followed by clear sections for Args and Returns. Each sentence adds value without redundancy. However, the 'Returns' section is vague ('Confirmation of deletion'), which slightly reduces efficiency by not specifying the confirmation format.

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 (a destructive operation with 2 parameters), no annotations, and no output schema, the description is incomplete. It covers the basic action and parameters but misses critical behavioral details like permanence, error handling, and authentication needs. The lack of output schema means the description should explain return values more thoroughly, which it doesn't do.

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 description adds meaningful context for both parameters beyond the input schema, which has 0% coverage. It explains that 'repo_slug' identifies the repository and 'variable_uuid' is the UUID from 'list_pipeline_variables', clarifying their roles and relationships. This compensates well for the lack of schema descriptions, though it doesn't detail format constraints (e.g., UUID format).

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 action ('Delete') and target resource ('a pipeline variable'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'create_pipeline_variable' and 'update_pipeline_variable' by specifying the destructive operation. However, it doesn't explicitly mention the repository context, which is implied but could be more specific.

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 minimal guidance on when to use this tool. It mentions that 'variable_uuid' should come from 'list_pipeline_variables', which hints at a prerequisite but doesn't explicitly state when to choose this over alternatives like 'update_pipeline_variable' or warn about irreversible deletion. No context on permissions or constraints is provided.

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