delimit_deploy_rollback

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The description 'Rollback to previous SHA' implies a destructive or state-changing operation, but it does not disclose whether the rollback is reversible, what permissions are required, or any side effects like downtime. The minimal description fails to convey essential behavioral traits for a rollback action.

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 efficient and front-loaded. However, it may be too terse, sacrificing necessary details. It earns a 4 for being concise without unnecessary text, but a 5 would require adding essential information in the same concise manner.

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 complexity of a rollback operation (destructive, requires state knowledge, parameters), the description is incomplete. It does not explain return values (though output schema exists), prerequisites, or the meaning of parameters. The tool lacks annotations, so the description should provide a comprehensive understanding, which it does not.

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 input schema has 3 parameters (app, env, to_sha) with 0% description coverage. The description mentions 'previous SHA' but does not explain that 'to_sha' is optional and defaults to null, nor does it clarify the roles of 'app' and 'env'. Since schema coverage is 0%, the description must fully compensate, but it fails to do so.

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 'Rollback to previous SHA (Pro)' clearly states the action (rollback), the resource (SHA/commit), and the qualifier (previous). It implicitly differentiates from sibling tools like 'delimit_deploy_build' and 'delimit_deploy_plan' by specifying a rollback operation. However, it does not explicitly distinguish from 'delimit_release_rollback' which is a sibling but not directly in the deploy group.

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 like 'delimit_deploy_plan' or 'delimit_deploy_verify'. There are no prerequisites mentioned (e.g., needing a previous deployment), no conditions for use, and no mention of when not to use it. The 'Pro' tag hints at a restriction but is not elaborated.

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