delete_build

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

Annotations already declare destructiveHint and readOnlyHint=false. The description adds that deletion is permanent and that the linked artifact is also removed, which is valuable beyond the annotations. It does not discuss behavior for already-deleted builds, but idempotentHint covers that aspect.

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?

One sentence front-loads the action and object with no filler. Every phrase contributes: permanent, delete, build job, linked artifact, and project context.

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 one-parameter destructive tool whose annotations already convey safety and idempotency, this description is complete. It clearly states what is removed and that the removal is permanent; a return-value specification is not necessary for a delete operation.

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 0%, so the description should compensate for the parameter. 'buildId' is implicitly the identifier of the build job to delete, and the integer schema makes it understandable, but no additional format, source, or lookup guidance is provided.

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 names a specific verb ('delete') and resource ('build job and its linked artifact'), clearly distinguishing it from sibling operations like create_build, list_builds, get_build, and download_build. The word 'permanently' adds important scope about the operation's effect.

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 gives clear usage context: use this when a build job and its linked artifact should be permanently removed. It does not explicitly list alternatives or when-not-to-use conditions, but the unique delete action is recognizable among the build-related sibling tools.

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