delimit_deploy_publish

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

No annotations provided, but description details side effects: premium gating, network writes to container registry via backend. Lacks mention of reversibility but still strong.

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?

Structured with headings (When to use, When NOT to use, Sibling contrast, Side effects). Every sentence adds value; no filler.

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?

Covers purpose, prerequisites, exclusions, sibling differentiation, side effects. Output schema exists, so return values are handled externally. Complete for agent decision-making.

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 covers both parameters fully (100%). Description only repeats schema text without adding new context about usage or defaults. Baseline 3 applies.

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?

Description starts with clear 'Publish previously built images to the registry (Pro).' Then distinguishes from siblings deploy_build and deploy_verify, making the purpose unambiguous.

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?

Explicitly states when to use (after delimit_deploy_build) and when not to (building images or starting deploy chain). Also names sibling alternatives.

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