delimit_deploy_rollback

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

Discloses side effects: requires premium, mutates environment via backend call. Lacks details on error conditions or authorization beyond premium, but adequate for a mutation tool without annotations.

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?

Very concise with clear sections (purpose, when to use, when not, sibling contrast, side effects). No wasted words.

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 essential aspects given presence of output schema (not needing return value explanation). Could include more on failure modes or idempotency, but sufficient for a rollback 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 coverage is 100%, so baseline 3. Description adds no new meaning beyond schema; 'to_sha' is already described. No extra guidance on parameter usage.

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?

Clearly states 'Roll back an environment to a previous SHA' and distinguishes from sibling delimit_deploy_publish, which moves forward. Specific verb and resource.

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 describes when to use (after delimit_deploy_verify shows regression) and when NOT to use (for deploying new version). Also contrasts with sibling tool.

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