delimit_deploy_build

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

With no annotations, the description transparently discloses side effects: license gating (require_premium), local disk and CPU consumption via docker buildx, and no network push. It also mentions response routing. Lacks details on error behavior or build timeouts, but otherwise thorough.

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-organized into logical sections (purpose, when to use, when not to use, sibling contrast, side effects). It is front-loaded with the core purpose. While comprehensive, it could be slightly more concise; the sibling contrast section, though helpful, is somewhat lengthy.

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 (build step with side effects) and the presence of an output schema (mentioned in context), the description adequately covers purpose, usage, side effects, and relationships to siblings. It does not detail the output format but that is handled by the output schema. Minor gaps: no mention of required permissions or error recovery.

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?

Both parameters (app and git_ref) are fully described in the schema (100% coverage). The description adds only boilerplate context (e.g., 'git ref (Pro)') but does not provide additional semantic guidance beyond what the schema already offers.

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 verb 'Build container images for an app at a specific git ref', identifies the resource (container images), and distinguishes from siblings by positioning itself as the second step in the deploy chain. The title implies this is the build step, and the description reinforces that.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear context for when this tool is appropriate, including the full chain (plan -> build -> publish -> verify -> rollback) and specific sibling alternatives for when not to use (e.g., delimit_deploy_publish, delimit_deploy_site).

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