Delete pipeline schedule variable

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

The description notes that the tool does not return the former value, which is a specific behavioral detail. However, it does not mention other side effects, idempotency (which annotations indicate is false), or error conditions, leaving the agent with limited understanding.

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 sentence, which is highly concise and front-loaded. It avoids unnecessary verbosity, but this comes at the cost of detail.

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 very sparse, lacking any contextual information about pipeline schedule variables, when deletion is appropriate, or potential consequences. It does not explain the relationship to pipeline schedules or provide examples, making it incomplete for robust 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 description does not clarify any of the three parameters (project, pipeline_schedule_id, key). Only the schema provides a description for 'project', while the other two lack any semantic explanation, making it difficult for an agent to know what values are expected.

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 the resource (pipeline schedule variable), which is unambiguous and distinct from sibling tools like create or update.

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, such as when a variable needs to be removed without retrieving its value. It lacks context like prerequisites or typical use cases.

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